YouTube Giveaway Winner Picker for One Video’s Entries

Open the free giveaway winner picker with a list you have already prepared from the correct YouTube video. You can paste entrant identifiers or import a CSV, choosing the entrant and comment columns yourself. No video URL is fetched, no channel is connected, and no subscription is verified. The local tool applies the settings you choose to supplied rows; the video scope, deadline, and any answer requirement must come from your separate preparation and review.

Anchor the measuring-kit draw to the right video

The workshop’s fictional restoration video shows how to measure a worn bearing seat. Its giveaway asks viewers to name a measurement check they would use, include GAUGE, and comment on that video before the stated deadline. A Short previews the repair and a community post announces the prize. Put the exact entry-video URL in the working sheet so those related discussions are not accidentally treated as additional places to enter.

Treat the video identifier as the stable reference in your preparation notes, not just a title such as ‘Workshop restoration’. Titles can look similar across episodes or be revised after publication. Record the relevant campaign wording alongside the reference. A teammate preparing entries next week should be able to tell whether they are checking the bearing-seat demonstration or the earlier vise restoration without opening every possible source and guessing from the prize image.

Decide whether direct replies under another viewer’s comment qualify. The host may answer tool questions, and viewers may debate a repair technique inside a long thread. Those messages are not automatically separate giveaway submissions. Use the announcement’s meaning consistently and keep thread context when a reply needs interpretation. Flattening every visible author into one list can include the host, tagged participants, and ordinary discussion that never met the entry requirement.

Keep livestream chat and comments beneath an archived video conceptually separate. A message sent during the live broadcast does not become an eligible comment merely because the same person also watches the restoration video. If your actual campaign accepts multiple surfaces, define and reconcile them before import. This example accepts one video’s qualifying comments only, so the prepared pool should not inherit accounts from a channel-wide conversation file or a previous giveaway.

Review the video’s comment coverage before making a shortlist

YouTube distinguishes Top comments from Newest first, and its help explains that a missing comment may become easier to find after changing the sort. Top comments reflects a presentation order, not an eligibility rule. For preparation, avoid using only the first visible comments or those with the most likes. Record the view and scope you checked, then assess qualifying submissions across that scope rather than turning a prominence ranking into a shortlist.

YouTube Studio separates published comments from held material. Depending on the video’s settings, comments can be held before they become publicly visible. Inspect the moderation areas available to the channel owner as part of preparing the source, and distinguish a comment’s submission time from the time someone approved it. A later approval does not by itself establish that the comment was late, just as a published comment is not automatically a qualifying giveaway answer.

The official comment-settings guidance distinguishes pausing comments from turning them off: pausing retains existing comments while preventing new ones, whereas turning comments off hides existing comments until they are restored. Do not treat those controls as interchangeable ways to close your working list. Use the campaign’s actual deadline and document the source state you reviewed. The picker cannot reconstruct an earlier comment view or decide which setting the host used during preparation.

Take special care with a source assembled by several moderators. One person may have checked published comments while another reviewed held submissions or replies. Keep their coverage notes and reconcile overlaps using source evidence. A combined spreadsheet should not reward the same captured comment twice simply because two teammates handled it. It also should not omit a reviewed entry because each moderator assumed the other had transferred it to the final sheet.

Use commenter handles without erasing meaningful characters

YouTube describes handles as unique channel identifiers, distinct from channel names, and shows them in comments and other surfaces. Where your source supports it, a consistent handle field is more useful than a channel’s display name for this draw. Two channels can present similar names in a preparation sheet. Do not let a copied display label such as ‘Garage Notes’ silently become the identity key when a more specific source reference is available.

Keep non-English handles intact. YouTube supports handles using multiple languages, so reducing the entrant field to English letters can damage valid identifiers or merge unrelated ones. Use UTF-8 when moving the list through a spreadsheet and inspect representative names after import. The picker’s Unicode normalization addresses equivalent text forms; it is not transliteration and does not decide that visually similar characters from different writing systems identify the same channel.

YouTube states that handles are not case-sensitive. If the prepared pool mixes capitalization, case folding can align that comparison behavior; optional leading-@ removal can reconcile prefixed and unprefixed copies. Still inspect the reviewed identities. A full channel URL in one row and a bare handle in another are not the same supplied string simply because a human recognizes the connection. Standardize those fields from the source before loading them into the picker.

An identifier remains an account reference, not proof of a unique human participant. Someone may operate multiple channels, and a familiar display name is not enough to merge their records. Do not use comment similarity, a shared email address, or a guessed relationship to combine accounts. Preserve any genuine identity correction in the preparation notes with supporting source evidence, especially if a commenter reports a handle change after the eligible pool has been assembled.

Assess the measurement answer before applying a text filter

The restoration prompt asks for a measurement check, not merely the campaign word. A fictional answer saying ‘GAUGE: I would check the bearing seat in two directions’ supplies both. Another saying ‘GAUGE, where did you buy the lamp?’ contains the word but asks an unrelated question. The host must decide which messages satisfy the published prompt during preparation. The picker does not understand repair techniques or judge whether a proposed check is a meaningful answer.

Apply that standard across unfamiliar and familiar commenters alike. An answer need not be the most polished explanation to meet a simple participation condition. If the campaign asks for one relevant check, do not quietly favor professional terminology or longer comments. Write a short acceptance note for reviewers, identify borderline examples, and resolve them before drawing. The task is to establish the eligible pool, not to select the technically strongest response unless that was the announced method.

The keyword field performs a literal, case-insensitive substring match in the chosen comment column. GAUGE will also match ‘gauges’, while ‘measuring tool’ does not match it at all. Quoting the keyword in a question can pass the same check. Use the option as a narrow cross-check when appropriate, not as a substitute for the full prompt. A source search or topic grouping also does not replace reading the actual submitted answer.

Record the announced cutoff with a date and time zone, and assess timestamps in the source sheet. Additional CSV columns do not apply a date rule inside the picker. If a submission’s current text differs from an earlier observation, rely only on evidence your preparation actually retained and apply the campaign’s stated handling of edits. Do not claim to reconstruct an earlier answer from its present wording or invent a revision history that you cannot see.

Preserve a whole answer in each prepared CSV record

Use one row for each candidate submission, with separate commenter and answer columns. Keep source links, timing evidence, and review notes in the private working sheet. A long answer might include a quoted measurement, several commas, and a second paragraph explaining a tool choice. Export it as normal quoted UTF-8 CSV so all of that text remains attached to one commenter rather than becoming a series of broken records.

Choose the entrant column and the comment column explicitly after import. A header called channel_title is not necessarily the handle you intended to use, and a field called reply_to may identify someone other than the author. Inspect actual sample values before selecting. Other fields are ignored by the picker, so a spreadsheet column labeled approved does not automatically exclude rows marked no. Prepare that eligibility boundary yourself instead of relying on the header’s meaning.

Test a representative subset against the source: a short answer, a multiline answer, a handle with non-English text, and a reply that your rules admit. Check that blank author fields are reported rather than filled with guesses. If an answer mentions another channel, the mention belongs in the comment text, not the entrant field. A row with the right words and the wrong author would assign the chance to the wrong supplied identity.

Plan around the picker’s own limits: at most 10,000 rows, two megabytes of input, 100 code points per entrant, and 1,000 per comment. These are not YouTube comment specifications. Do not shorten an answer in a way that changes an eligibility decision merely to fit it. Keep the complete source separately and settle a suitable prepared representation before drawing; never select a convenient first batch and describe it as the complete video pool.

Turn fifteen candidate rows into eight eligible identities

Imagine fifteen candidate rows from the designated video. Arbor has three, Bench has two, Clamp has two, Dowel has two, and six other accounts have one each. That is ten supplied identities. Two Arbor rows are accidental copies of the same author-and-comment pair; the third contains different text. Exact duplicate removal drops one copy, leaving fourteen rows and ten identities. An identical sentence submitted by another author would not be that same duplicate.

Both Bench comments fail the answer requirement, so external preparation removes those two and leaves twelve rows across nine identities. One single-row account is the channel’s host, excluded under this campaign’s arrangement, leaving eleven rows across eight identities. One Clamp comment was late and also leaves. The approved result is ten rows and eight identities: two rows each for Arbor and Dowel, one for Clamp, and five other single-row accounts.

The host promised one chance per eligible channel, so unique mode is the match. Each of the eight supplied identities has one first-selection chance, regardless of whether it has one or two approved comments. Entries mode would instead give Arbor and Dowel two of ten first-selection chances each. Keep that alternative as an explanation, not a reason to change the campaign after seeing who participated. The duplicate and entry-rule guide explores the distinction.

Separate those reductions in your records because they arise from different evidence. The duplicate pair is detected from the normalized identifier and trimmed comment; answer quality and the deadline were assessed outside the tool; the host exclusion can remove every row matching its normalized identifier. The picker cannot report reasons for rows you never supplied, so retain those external reasons in the source sheet. Final counts should reconcile without pretending every decision was automated.

Have the co-host approve the exact pool being drawn

Ask the co-host to compare the reviewed eight identities with the approved preparation sheet, rather than approving a screenshot of the raw fifteen rows. Check missing or invalid records, duplicate handling, exclusions, keyword settings, and the final chance mode. A discrepancy should lead to the specific row or identifier that caused it. ‘The totals are close’ is not enough when one missing channel represents an entire participant’s opportunity in unique mode.

For two measuring-kit winners and three reserves, the combined five ranks fit within the example’s eight eligible identities. Counts are limited to one through fifty winners and zero through fifty reserves, with their total bounded by eligible identities rather than comment rows. Confirm that both kits use the same eligibility conditions. If the prizes have different restrictions, prepare those decisions before selection instead of assigning a restricted kit to whichever selected account happens to qualify.

Once reviewed, the pool is frozen for the draw. Editing input or settings invalidates that review and any existing result or export tied to the previous version. A correction from the co-host therefore means reviewing again before clicking Draw winners. Save the approved preparation version outside the page as needed. The browser’s memory-only operation does not provide a persistent project history that another moderator can reopen tomorrow to recover unsaved decisions.

The selection uses secure browser random values with unbiased index sampling, and every selected identity leaves before the next rank. In entries mode, all rows for that identity leave together, so one channel cannot take both kits or return as a reserve. If secure randomness is unavailable, no draw proceeds. A later new draw needs confirmation. None of this certifies the source sheet independently; the co-host’s preparation check still matters.

Publish the outcome while keeping the review trail private

Save the recorded result before closing the tool. Copy result provides a short text handoff, result CSV supports a fulfillment sheet, full JSON preserves the detailed draw record, and PDF supplies a readable record with guidance. Keep the campaign reference beside these files so a future editor knows which video and giveaway they concern. A bare filename such as ‘winners-final’ becomes ambiguous when the channel runs several similar tutorials in a season.

The UTC timestamp marks the draw, while the draw ID distinguishes that outcome from another recorded selection. Settings, counts, winners, ordered reserves, eligible pool information, and excluded-row reasons support review of what the operator supplied. They are not tamper-proof proof of the entire campaign history. Keep the original candidate sheet and external eligibility decisions as companions, especially because the tool cannot reconstruct comments removed before import or prove which video they came from.

Prepare an announcement using the winner identifiers checked against the source and the prize description participants recognize. Keep delivery details and private contact information out of the public result. Inspect the full record before sharing, since it may expose non-winning commenters and their answers. A public winner message and an internal review file have different audiences. Uploading every entrant’s information is not necessary simply because a JSON download is available for your own records.

Follow the stated response and fulfillment process, approaching reserves in their recorded order when a place opens. Note the reason, contact date, and resulting handoff without changing the original draw. The guide to reserves and redraw records explains when a replacement and a new draw are different actions. When another restoration episode launches a new giveaway, start from that video’s own preparation sheet and return to the main winner picker with a fresh eligible pool.

Questions about YouTube 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.