Four image cards have red crosses. A larger card connects through document and person icons to a checked card.

Start with manual listening. The YouTube Search Actor can collect public search results for your written queries. An Actor is a hosted data collection program. This Actor does not match an audio file against videos. You must inspect the candidates yourself. A candidate is a video that might contain the clip.

Your result should be a source history table. This table records each candidate, the matching evidence, and the questions that remain open. It can support a useful finding even when you cannot establish the recording source.

Define what you mean by original

The word “original” can hide several different questions. You might want the longer video that contains a short repost. You might want the first upload you can locate. You might want to identify the person who recorded the event. These findings need different evidence.

Write one question before you search. For example: “Which longer video contains this clip with the same preceding sentence and scene?” This question gives you a clear check. Finding the earliest upload requires a separate date comparison. Identifying the recorder requires evidence about that person’s role.

Use these distinctions throughout your notes:

Define what you mean by original
FindingEvidence you needWhat remains open
Possible matchA phrase or another detail worth checkingWhether the full passage matches
Contextual matchMatching words, scene, and surrounding sequenceRecording origin and ownership
Earliest located uploadAn established upload date compared with the checked candidatesWhether an earlier upload exists elsewhere
Recording sourceEvidence that identifies who recorded the materialAny separate ownership question

Context means the words, pictures, and events around the selected passage. A contextual match connects the repost to material in another video. It does not establish who filmed that material.

Keep the claim attached to the repost separate from your finding. “Uploaded by the recorder” may be the uploader’s claim. Record it as a claim until you have supporting evidence.

Save the clip before you search

  1. Save the public clip URL. A URL is the web address of the clip.
  2. Record when you inspected it. Call this the observation date.
  3. Copy the claim about its origin into your notes. Identify where that claim appears.
  4. Describe a few audible and visible details.
  5. Mark every uncertain detail as uncertain.

Useful details include a distinctive sentence, a visible sign, a speaker introduction, or the order of two actions. Record what you can hear or see. Do not treat an uploader’s caption as a checked description.

Keep the observation date separate from the upload date. The observation date says when you saw the public page. It does not say when the video was uploaded or recorded. If an upload date is unavailable, write “unknown.” Do not enter zero.

Preserve the repost as a separate source record even if you later find a longer match. Different uploads can have different cuts, titles, or attribution claims. Attribution is a statement that names a source or creator.

Build a small set of phrase searches

Listen for a short phrase that is more distinctive than a general topic. A specific statement gives you a clearer comparison than words such as “bridge news.” Write the words you hear before you search.

If one word is unclear, keep alternate readings. For example, your note might say that you cannot distinguish “closed” from “closes.” Do not silently choose the reading that produces a result.

Prepare a small search set:

  1. Search the clearest phrase.
  2. Search a reasonable alternate reading.
  3. Search another distinctive phrase from the clip.
  4. Add a clearly heard name or topic when it helps distinguish candidates.

These searches are proposed actions. No search described in this guide was run for the clip you want to trace.

Do not expect quotation marks in a YouTube Search Actor query to guarantee an exact phrase match. The documented Actor contract gives no exact phrase or audio matching guarantee. Review the returned videos before you decide that the words match. YouTube Search Actor — public contract checked 2026-10-25; no paid run

You can make a separate Google Search pass. Google documents quotation marks for exact word or phrase searches. It also documents `site:` to restrict results to a chosen site. A search such as `"the bridge closed before sunrise" site:youtube.com` illustrates those operators. That phrase is original fiction, not a reported search result.

These operators narrow Google’s indexed results. They do not promise that every spoken word in a video is indexed. If you find no match, try a reasonable alternate phrase. A failed search does not prove that the video is absent. Google Search Help — checked 2026-10-25; operators apply to indexed search results

Use a small Actor input for candidate collection

The YouTube Search Actor searches public YouTube video results. It can help you collect candidate links and keep their search details. It does not supply caption text, comment text, media downloads, or private YouTube Studio analytics. Analytics are records used to measure activity or performance.

The following small input passed a check against the supplied public input schema. A schema defines accepted fields and values. This check did not execute the Actor and did not establish useful search results.

json
{
  "enableQueryExpansion": false,
  "enrichWithVideoMetrics": false,
  "includeShorts": false,
  "maxPagesPerQuery": 1,
  "maxResults": 3,
  "queries": [
    "How can I find the original YouTube video from an audio clip?"
  ],
  "resultsPerQuery": 3,
  "searchDistribution": "balanced"
}
Use a small Actor input for candidate collection

Replace the general question in `queries` with the distinctive words from your clip. The sample question asks how to search. It does not describe the clip you need to find. Add only a few deliberate variants at first.

Understand the collection limits before you run it:

  • `maxResults` limits the run to three unique videos across all queries.
  • `maxPagesPerQuery` limits each query to one attempted search page.
  • `searchDistribution` set to `balanced` rotates across queries until the global limit or source limits stop collection.
  • `resultsPerQuery` defines the per-query unique-video limit in sequential mode. Do not treat it as a promise of three results for every query in balanced mode.
  • `enableQueryExpansion` set to false keeps automatic query suggestions off.
  • `enrichWithVideoMetrics` set to false disables the richer public metric collection stage.
  • `includeShorts` set to false excludes Shorts-style search cards from this proposed pass.

This small input may miss relevant videos, including a Shorts candidate. Record that limit. If you need another pass, change a stated condition and save the new input separately. Do not describe three saved videos as a complete search of YouTube.

The input does not explicitly disable `enrichMissingChannelFields`. The supplied schema gives that field a default of true. Thus, turning off richer metrics does not by itself turn off every optional public-detail request. YouTube Search Actor — build 1.0.34 checked 2026-10-25; public schema and README only

A Task is a saved input preset. The public youtube-competitor-video-research Task was present in the frozen evidence. Its presence does not prove that its saved input suits your clip. No authenticated saved-input check or paid execution was supplied. Inspect and replace sample values before use.

Compare the passage and its surroundings

A matching title is a reason to inspect a video. It is not enough to accept it as a match.

  1. Open each plausible candidate.
  2. Locate the phrase by listening or by checking available captions.
  3. Play the phrase and compare the audible words.
  4. Compare the speaker evidence and visible scene.
  5. Play enough material before and after the phrase to compare the sequence.
  6. Save the matching details and every conflict.

Captions are written words stored with a video. They can help locate a passage. They do not prove that the audio or scene matches. The Search Actor does not return those captions. Any caption inspection or playback in this method is a separate action.

If exact wording matters to your conclusion, use the focused checks in How to quote a YouTube video accurately. Here, the purpose is to compare material across uploads. You do not need to build a quotation record for every line.

Do not identify a person only because a voice sounds familiar. Record an introduction or another explicit identity statement when available. If the identity remains unknown, keep it unknown.

A missing caption does not end the comparison if you can play the video. Listen manually and label any words you write as your own transcription. A transcription is text written from speech. If neither playback nor another needed source is available, leave the candidate unresolved.

If you later collect captions for several candidates, keep that collection separate from this match decision. Build a YouTube transcript corpus from search results explains how to account for each selected video and its caption outcome. A successful caption result does not establish a source match.

Follow visual leads when they add evidence

If the words are unclear or repeated in many videos, inspect several detailed frames. A frame is one still image from a video. Choose frames that show different useful details rather than several nearly identical pictures.

AFP describes searching detailed video frames and following matches to reporting that explains their context. Its method requires investigation after a search result appears. A matching frame is a lead. It is not a complete finding about origin. AFP Fact Check — checked 2026-10-25; manual frame investigation, not an Actor feature

Keep this visual investigation in separate notes. Record which frame led you to which page or candidate. Then return to playback and compare the sequence. A frame match does not by itself settle the audio relationship or identify the recorder.

Save a source history table

Keep the raw search output unchanged. Add your review findings in a separate table. Raw output means the records returned by the Actor before your edits.

Preserve `rootQuery`, `query`, `querySource`, `pageIndex`, and `pageRank`. These fields record the search terms and result position. Keep `postId`, `postUrl`, `channelId`, `channelUrl`, `publishedAt`, `observedAt`, `status`, and `statusReason` when returned. A result position is not an upload date or proof of relevance.

Add these manual review fields:

Save a source history table
FieldWhat to save
Repost sourcePublic URL and the origin claim being checked
Candidate sourceCandidate URL, video ID, and available channel details
DiscoverySearch terms, collection limits, and observation date
Matched passageWords heard and passage times in each video
Surrounding sequenceWhat occurs before and after the phrase
Scene comparisonMatching details, differences, and unclear details
Channel evidenceRelevant source statements and attribution links
Date evidenceUpload date when established and its source
ConflictsEvidence that weakens the proposed match
DecisionPossible match, contextual match, contradicted candidate, or unresolved
Open origin questionsRecorder, earlier source, or ownership questions still unanswered

These review fields are your notes. They are not extra Actor output fields.

Leave missing dates and channel values missing. In a written table, use “unknown.” If a raw value is `null`, preserve it. A missing view count is not zero views. Counts also do not identify people: three videos are not necessarily three creators or three independent sources.

Public search and channel records are public evidence. Private Studio analytics are owner-only records and are outside this Actor’s output. Do not present public search collection as access to them. Neither an uploader’s name nor a public channel record proves copyright ownership.

Worked example: original fiction

Everything in this example is original fiction. The phrase, candidates, dates, times, and findings are invented. They are not Actor results or evidence about a real event.

A fictional repost contains the phrase “the bridge closed before sunrise.” Manual phrase searches lead to two fictional longer videos, A and B. Both contain those words. Only B matches the scene and the sentence immediately before the phrase.

The repost passage runs from 22 to 30 seconds. Its length is 30 − 22 = 8 seconds. Candidate B contains the matching passage from 74 to 82 seconds. Its length is 82 − 74 = 8 seconds. Equal lengths alone do not establish a match.

The reviewer also checks B from 68 to 90 seconds. That wider interval lasts 90 − 68 = 22 seconds. It supplies the preceding sentence and surrounding sequence needed for the comparison.

Worked example: original fiction
ItemCandidate ACandidate B
PhraseMatchesMatches
SceneConflicts with the repostMatches the repost
Preceding sentenceDoes not matchMatches
Fictional upload date2024-02-122024-02-10
Recorder attributionUnknownUnknown
DecisionContradicted for the proposed contextual matchContextual match with open origin

There are two candidate videos and one contextual match: 1 matching video out of 2 reviewed candidates. This is a count within the fiction. It is not a success rate for the Actor or the method.

B’s fictional upload date is earlier than A’s. That supports an earlier appearance among these two uploads. It does not prove that B’s uploader recorded the event. The repost’s upload date and the observation dates are not supplied, so they remain unknown.

The careful conclusion is: “Candidate B contains a contextual match to the repost. The recording source remains unresolved.” Do not change that finding to “B is the original recorder.”

Handle failed searches and incomplete evidence

Use a decision that fits the evidence you actually checked:

Handle failed searches and incomplete evidence
StateRequired response
Phrase found; playback not checkedKeep a possible match
Words, scene, and sequence matchRecord a contextual match with open origin questions
Checked scene or sequence conflictsRecord the conflict and reject that proposed contextual match
Candidate cannot be inspectedKeep it unresolved
No candidate appears within the limitsReport no match in the checked search set
Date is missingKeep date order unresolved
Recorder attribution is missingKeep recording origin unresolved

A search with no useful result is still a bounded result. State the phrases, sites, formats, result limits, and inspection date. Identify material you could not check. Do not turn “not found in this search” into “does not exist.”

Stop when you can make a supported decision, or when the remaining question needs evidence your search cannot supply. More copies of the same passage do not automatically provide more evidence about who recorded it.

Sources & further reading

By Chronometrica · Updated

Back to top ↑