Instagram Giveaway Winner Picker for Prepared Comments

Use the free giveaway winner picker after you have collected and checked the comments through your own authorized workflow. Paste entrant identifiers line by line, or import a prepared CSV and select its entrant and comment columns. The picker runs locally in your browser. It does not open an Instagram post, collect its replies, inspect profiles, or confirm follows and tags. Your preparation determines who enters; the tool reviews that supplied pool and draws from it.

Give the mug giveaway one clear entry boundary

The studio’s announcement asks readers to comment MUG and mention one friend on a particular Reel before the stated closing time. A later photo shows the same prize but only reminds people about the giveaway. Start the preparation sheet with the entry Reel’s exact URL and the original instruction. Otherwise, a helpful assistant may combine both comment sections and quietly give reminder-post readers a route that the announcement never offered.

Define the participant as the author of a qualifying comment. The mentioned friend is part of the author’s submission, not automatically another entrant. Also decide whether replies beneath other comments qualify or whether the instruction refers only to direct comments on the Reel. Apply the published interpretation across the whole source, rather than deciding differently when a familiar customer appears inside a reply thread. Preserve uncertain cases for review before loading the final list.

Record the closing instant with its date and time zone in the working sheet. If the studio operates in Bucharest but has followers elsewhere, ‘Sunday evening’ is not a useful preparation boundary. Use the announced instant, then compare source timestamps against it outside the picker. Extra CSV columns are not date filters here. A timestamp column can support your private review, but selecting the comment column does not make the tool enforce the deadline.

Keep the prize structure beside that boundary: two equal mug sets, two winning identities, and two ordered reserves. A reserve is not a third winner and should not be announced as one. If the real campaign offers different prizes with different eligibility conditions, settle those pools separately before drawing. Choosing a different prize label afterward cannot repair a pool whose participants never qualified for that particular reward.

Build author and comment pairs before cleaning anything

Prepare a source sheet with separate fields for the author’s identifier and the complete comment text. Retain the post reference, observation time, and your eligibility notes in other columns for your own records. Work on a copy when removing irrelevant rows. The original pairing matters: a comment saying ‘MUG @river.pal’ belongs to its author, even though the friend’s handle may be the most visually prominent text in the message.

Meta documents Hidden Words filtering for comments and message requests, including custom terms. It also describes Limits as hiding comments and requests from some non-followers or recent followers. For giveaway preparation, the practical consequence is that the first visible view may not represent every submission you need to assess. Check the moderation areas and settings available to the account owner, then record which material your preparation actually covered. Do not call a partial view complete.

Separate an Instagram moderation decision from a giveaway eligibility decision. A harmless entry may need assessment because it was filtered; an approved comment may still lack the required campaign word. You are not required to change protective settings just to operate the picker. Instead, review accessible source material consistently and keep a short note explaining how qualifying entries found during that review were included in the prepared sheet.

Spot-check the sheet against the source before applying bulk cleanup. Compare one short comment, one multiline comment, one reply, and one message containing several mentions. Make sure line wrapping has not turned a single comment into several spreadsheet records or moved an author onto the next person’s text. A clean-looking list with mismatched columns produces a convincing draw from the wrong relationships, which later duplicate settings cannot reconstruct.

Read tag text without turning friends into entrants

Consider three invented submissions. An author writes ‘MUG @lena.cooks’; another writes ‘MUG @lena.cooks @omar.bakes’; a third writes ‘Love these, @lena.cooks’. Under the studio’s instruction, the first two can meet the word-and-mention requirement while the third lacks the campaign word. The second comment still supplies one author row. Two mentions inside that row do not create two author entries unless the campaign expressly established that different arrangement.

The picker does not interpret a typed mention as a verified relationship or a valid Instagram account. You must assess any tag requirement while preparing the pool. If the instruction requires one friend, determine what evidence the source provides and how incomplete or ambiguous text is handled. A string beginning with @ is text, not confirmation that the named person exists, is eligible, or received a notification from Instagram.

Avoid counting handles with a simple search-and-split operation. An @ character can appear in copied context, a quoted comment, or a mention directed at the studio itself. A comment containing three names also does not tell you which are friends or whether repeated mentions are allowed. Keep the entire text attached to its author and mark the eligibility decision explicitly in the preparation sheet, where a second reviewer can understand it.

Questions deserve their own treatment. Someone might ask ‘Does MUG @myfriend count if they live abroad?’ That message contains both the keyword and a mention, yet may be a question rather than an intended entry under your instructions. Resolve that distinction from the campaign wording and source context. The guide to duplicate entries and chance rules helps separate qualifying rows from the later decision about how many chances each author receives.

Keep handle cleanup narrower than identity verification

Use one consistent author identifier throughout the prepared pool. A handle is generally more useful for this task than a decorative display name copied from a screenshot, but it remains a supplied identifier rather than a verified person. If two rows both say ‘Mia’, the picker cannot know whether that means one account or two customers with the same name. Resolve the source reference before importing, without inventing extra certainty.

The tool trims surrounding whitespace and normalizes Unicode text. Optional settings can remove a leading @ and fold letter case when comparing entrant identities. In a fictional sheet, ‘ @Fern.Cup ‘ and ‘fern.cup’ can therefore be treated as the same identity when those options are enabled. Inspect the reviewed pool after choosing the settings. The purpose is to reconcile formatting differences in the same supplied identifier, not to guess who controls several accounts.

Do not remove meaningful punctuation from handles simply because they look similar. ‘fern.cup’, ‘fern_cup’, and ‘ferncup’ are different supplied strings, and a broad spreadsheet cleanup could collapse unrelated accounts. Likewise, matching profile photos or similar comments is not evidence that two handles belong to one person. Keep unresolved cases in a separate preparation note and use a documented campaign decision instead of an improvised identity-matching shortcut.

Account changes require source evidence rather than a guessed merge. If someone reports that their handle changed during the giveaway, compare the information available in your original record before replacing anything. Keep the old reference and the reason for the change privately. Never combine entries through a shared email address or a friend’s assurance alone. Your final list should be traceable to the campaign submissions, not to assumptions made during winner contact.

Use CSV columns and the campaign word deliberately

For the mug campaign, CSV is useful because both the author and comment matter. Export UTF-8 with a header row, then explicitly select the author field as the entrant column and the actual submission text as the comment column. The picker ignores other columns for eligibility calculations. Keep shipping details out of this file entirely; they serve prize fulfillment later and are unnecessary for deciding whose comment enters the draw.

A normal CSV export preserves commas, quotation marks, and embedded line breaks through quoting. Avoid building the file by manually joining cells with commas. A comment such as ‘MUG, please, for @lena.cooks’ must remain one comment field, not three accidental fields. Check the parsed review against the sheet and stop if an identifier appears in the comment column or an entire row seems shifted after a punctuation-heavy message.

The keyword option performs a literal, case-insensitive substring check in the selected comment. Searching MUG can include ‘mug’ and ‘mugs’; it does not mean ‘the complete standalone word MUG’. It also cannot distinguish a sincere entry from a sentence saying ‘I forgot to write MUG’. If the announcement demands an exact answer or a more nuanced condition, make that eligibility decision outside the picker and import the resulting pool.

Leave the keyword blank when you have already applied the complete campaign condition and only need a draw. If you keep it enabled as a useful cross-check, verify that it matches your preparation decision rather than replacing it. The tool accepts at most 10,000 rows and two megabytes of input, with limits of 100 code points per entrant and 1,000 per comment. These are picker limits, not Instagram limits; do not silently discard excess submissions.

Explain the difference between twelve comments and nine authors

Here is a fictional count check before eligibility rules. Fern has three rows, Clay has two, and seven other authors have one each. That makes twelve rows but nine supplied identities. Two of Fern’s rows contain exactly the same trimmed comment, while the third has different text. With exact duplicate removal enabled, one repeated Fern row disappears, leaving eleven rows across the same nine identities. Similar wording from different authors does not create an exact duplicate.

Both Clay comments lack MUG, so the keyword check removes those two rows and Clay leaves the pool entirely. Now there are nine rows across eight identities. One of the seven single-row authors is the studio’s helper, excluded under the campaign’s participation rule. Excluding that normalized identifier removes its row. The reviewed result is eight eligible rows and seven eligible identities: two rows for Fern and one for each of six others.

In unique mode, those seven identities each receive one chance for the first selection. Fern’s extra qualifying comment does not improve that first-draw chance. In entries mode, Fern holds two of the eight eligible rows and therefore two of the eight first-selection chances; each other identity holds one. Choose the mode that matches the announced arrangement. Extra effort in a comment is not automatically a reason to add weighting that participants were never told about.

Exact duplicate removal is a separate control from unique mode. It defaults on, but a campaign that intentionally counts repeated identical submissions may require it off after source checking. In either mode, selecting an identity removes all its remaining rows before the next winner or reserve is selected. Fern cannot win both mug sets by appearing twice. Explain the first selection separately from later ranks, whose pools change as identities leave.

Freeze the reviewed pool before selecting the mug sets

Read the review as a reconciliation, not just a green light. Compare input rows, invalid or missing identifiers, removed duplicates, keyword exclusions, manual exclusions, and the final identity count with your preparation sheet. Open unexpected cases before drawing. An empty author cell should not become an anonymous chance, and a studio exclusion should remove every row belonging to that normalized identifier rather than only the first comment you noticed.

For the example’s seven eligible identities, two winners plus two reserves fit the pool. Winner and reserve totals together cannot exceed eligible unique identities, even when entries mode shows more rows. The picker supports one to fifty winners and zero to fifty reserves within that identity limit. Enter the intended counts before review and have the person responsible for fulfillment confirm what each winner receives and when a reserve may be approached.

Review freezes the prepared pool. Changing source text, selected columns, normalization, exclusions, or draw settings invalidates the review and any result or export tied to it. When another comment needs correction, return to the preparation decision and review again. Do not treat a screenshot of an earlier pool as approval of the changed list. Click Draw winners only when the actual reviewed version is the one you intend to use.

The draw uses secure browser random values with unbiased index selection and refuses to proceed if secure randomness is unavailable. That describes the selection method, not independent certification of your preparation. A second draw after a result needs confirmation and creates another outcome. Do not redraw because the selected handle is unfamiliar or has fewer comments than expected. Address a genuine problem through your stated reserve or correction process and retain the original record.

Hand off prizes without publishing the whole comment pool

Save the result before leaving the page because entry data stays in memory rather than a saved browser project. Copy the result for a short handoff, download result CSV for the fulfillment sheet, and retain the full JSON record privately when you need the pool and exclusion detail. The PDF provides a readable record with guidance. Choose the artifact by its audience rather than assuming every export is suitable for a public announcement.

The record includes a UTC timestamp, draw ID, settings, counts, winners, reserves, and supporting pool information. It is an operator-generated record, not tamper-proof proof that nobody changed an earlier spreadsheet. Keep your original campaign sheet and review decisions alongside it. A colleague should be able to explain why Clay was excluded and why Fern had one or two chances without reconstructing the campaign from a cropped winner screenshot.

Contact the selected author using the account reference you checked, and collect delivery information through your normal private fulfillment route. A public announcement usually needs the approved winner identifiers and prize details, not everyone’s comments or the reserve contact list. Before sharing a full draw record, inspect it for participant information. Publishing a downloadable pool can expose people who only expected their comment to be assessed for the giveaway.

If a winner cannot take the prize under your stated process, approach the next ordered reserve and record the reason and date. Keep the draw order intact instead of choosing the reserve whose profile looks most convenient. The reserve and redraw record guide covers that handoff in more depth. For the next studio giveaway, reopen the winner picker with a newly prepared pool; do not reuse last month’s entrants by accident.

Questions about Instagram Giveaway Winner Picker

Continue with another giveaway workflow

Return to the Giveaway Winner Picker to review your entries, or explore another guide below. Browse all free tools for other preparation tasks.