If your OBS loop was archived, use YouTube Studio to find the Content ID claim, see who claimed it and inspect the content and segment details. This is a post-stream workflow for the archived video; it does not identify a match in real time or explain a live warning while you are broadcasting.
The practical route is Content → Claims → the archived stream → Restrictions → See details → Content used → See details. OBS controls can tell you what file or playlist was sent to YouTube, but the claim and claimant information are in Studio. Start by confirming that the stream has ended and an archive exists.
Confirm the OBS loop was archived
First, establish which recording you are investigating. In YouTube Studio, look for the completed livestream in your channel’s content. The archive is the video YouTube retained after the live broadcast; it is that video, rather than the OBS scene or playlist, that you will open to inspect a post-stream claim.
YouTube Help explains that an archived live stream can receive a Content ID claim after the broadcast ends. If you chose not to archive the stream, or no archived video is available in Studio, this particular workflow has no video on which to inspect the claim details. Do not assume the local OBS recording, if you made one, will contain YouTube’s claim information. The platform’s claim record is attached to the YouTube video.
It is useful to note the stream’s title and approximate broadcast date before proceeding, especially if your channel runs the same loop repeatedly. A devotional channel might have several broadcasts with nearly identical titles, while a local news channel may have separate daily archives. Match the claim to the correct completed broadcast, not just to a familiar filename or scene name in OBS.
If you are still working out how a loop behaves for someone arriving part-way through it, the ideas in making a 24/7 stream useful to viewers who join mid-playlist are relevant to the broadcast itself. They do not replace this Studio check: playback design and copyright claim records are different things.
Open Content and filter for Claims
Sign in to YouTube Studio for the channel that hosted the broadcast and select Content from the left-hand navigation. Use the filter bar above the content list and choose Claims. This narrows the list to videos with claims, so you can look for the completed stream without treating every archived broadcast as if it were claimed.
The names and placement of controls can change as YouTube updates Studio, but follow the labels shown in your current interface. YouTube’s Help guidance on copyright issues with live streams distinguishes post-stream claims on archived videos from live-stream copyright warnings. If the screen differs from the steps here, consult the current Help page rather than guessing from an older screenshot.
Find the correct stream in the filtered list by its title and broadcast context. If there are many similar entries, check the video details before opening anything: a claim on yesterday’s archive does not establish that today’s loop has the same match. A recurring title, reused file, or unchanged OBS scene is not enough to identify which archived video Studio is showing.
The claims filter is a way to find a record in YouTube Studio, not a scanner for your OBS media folder. It will not report a file merely because that file appears in a playlist, nor does a clean-looking OBS loop prove that no claim exists. The claim must be associated with the YouTube archive before you can follow its details.
Find the stream and open claim details
In the row for the archived stream, look at the Restrictions column. Hover over or open the Claims label there, then choose See details. Studio opens information about the claim attached to that particular video. Take care not to use an adjacent video’s row if the title or date is similar.
If the row does not show a claim, recheck that the Claims filter is active and that you selected the right channel and archive. A missing claim in the list does not reveal which reference would have matched, and OBS cannot supply that answer from its loop controls. The evidence for an identified match comes from the claim details, if YouTube has made them available for that archive.
Once the details page is open, read it before taking an action. The claimant name, the claimed content, and the segment information help explain what YouTube says was matched. Keep the archive title and the details page together in your notes if you need to compare multiple broadcasts later.
A claim is not the same as a copyright strike or a takedown. YouTube’s copyright claims overview describes the distinction and the possible consequences of a dispute. An unfamiliar name is a reason to inspect the evidence, not proof by itself that the claim is wrong.
Review Content used and claimant
On the claim details page, open Content used and then select See details. Look for the Claimant field and read the accompanying information about the claimed content. This is the documented route for identifying the claimant associated with the claim on the archived video.
The claimant is the party named in the claim record; the name alone may not tell you the exact source recording or the reason a reference matched. Read the content description and the segment data alongside it. If you do not recognise the claimant, do not infer that the claim is invalid, and do not infer that the claimant owns every item that appears in your OBS loop.
For a loop built from multiple clips, keep a simple inventory of what was playing around the relevant point in the archived stream. That might include the playlist order, a scheduled insert, a transition, or a separate audio bed. This is a practical way to compare your own material with the Studio record, not a substitute for the claimant and segment evidence displayed by YouTube.
A playlist can also make it harder to understand what a viewer heard at a given time. If you maintain a sequence rather than one continuous file, a guide to setting up an automatic video playlist for YouTube Live with FFmpeg may help you keep the sequence legible. For this troubleshooting task, the important point is to map the claim’s time information back to the archive, not to assume the playlist title identifies the claimed work.
Inspect the matched segment information
Review the segment or time-range information shown in the claim details. A claim can apply to a portion of a video rather than the whole archive. Use the displayed range to navigate to the corresponding point in the archived stream and compare what was actually playing or audible there with the content description in Studio.
For example, suppose a long ambience loop contains a short introductory recording before several hours of rain sounds. If Studio identifies a limited segment, inspect that part of the archive rather than concluding that the entire loop is the source. The example is only a way to work through the interface; it does not predict what YouTube will match on your channel.
Use the details Studio provides as evidence. The documented workflow does not promise that every claim will expose a source-video title that is immediately recognisable, and a claimant name on its own is not a precise match diagnosis. If the content description is broad or the segment does not make the source obvious, record what the interface actually says and avoid filling gaps with guesses.
When checking the archived video, remember that it may not look exactly like the OBS preview. A transition, a playlist item that changed during the broadcast, or a section removed from the archive can affect what you find at a particular point. Compare the claim’s segment with the archive as it exists in Studio, and separately check your OBS playlist or local notes if you need to reconstruct what was sent.
If your setup repeats or schedules distinct files, a reliable record of sequence can save time in later investigations. The article on scheduling YouTube livestream playlists using Docker addresses playlist scheduling, but it cannot establish a Content ID match. Treat schedule records as supporting context and the Studio claim details as the platform’s claim record.
Interpret separate claimants or segments
More than one entry may need attention. YouTube notes that different claimants can cover different segments, and claims can vary by country or region. Read each entry separately: identify the claimant, the content described, and the segment or territory information attached to that particular claim. Do not collapse multiple records into one assumed source just because they concern the same archive.
A practical notes table keeps the review grounded in what is visible. Fill it from the Studio page rather than from memory or from the name of an OBS file.
| What to record | Where to look | Why it matters |
|---|---|---|
| Archived stream title and broadcast context | Content list and video details | Confirms you opened the intended broadcast |
| Claimant | Content used → See details | Names the claimant shown in Studio |
| Claimed-content description | Claim details | Gives context for the match; it may not by itself identify a source recording |
| Segment or time range | Claim details | Helps you inspect the corresponding part of the archive |
| Any territory or separate claim information | Each claim entry | Prevents treating distinct claims as one record |
If the same archive shows separate claims, compare their segments and descriptions rather than assuming one claimant’s details explain the others. A music bed under a visual loop, for instance, may be relevant to a different segment than a short clip placed between scenes. That is a possibility to check against the displayed details, not a claim about what happened in your broadcast.
If you later consider disputing a claim, first make sure you understand what was claimed and whether you have a valid basis. A dispute made without a valid basis can lead the copyright owner to request removal. For the current process and distinctions between claims and strikes, use YouTube’s official copyright claims guidance and the options Studio presents on the actual claim. This article is an identification workflow, not legal advice or a guarantee about an outcome.
Distinguish archive claims from live warnings
A warning during a broadcast and a claim on its archive are different situations. YouTube scans live streams for third-party content; a live detection can produce a warning, replace the stream with a placeholder, and, if the material continues, lead to interruption or termination. A Content ID claim on an archived livestream is made after the live stream ends, if you choose to archive it.
| Situation | When it occurs | What to check |
|---|---|---|
| Live-stream copyright warning | During the broadcast | The live notice and whether the stream was replaced, interrupted, or terminated |
| Claim on an archived stream | After the broadcast ends, when an archive exists | The video’s Restrictions and claim details in YouTube Studio |
| Partner live Content ID matching | A specialised process for certain Content Manager partners | Do not treat it as the normal archive claim workflow; it creates no claims |
The distinction matters if someone tells you that Studio should reveal a match while OBS is still live. The steps in this article concern the archive after the stream ends. They do not identify a live match in real time, and the normal archived-video claim workflow is not a live monitor.
If a notice appeared during the broadcast, use YouTube’s live-stream Help information to understand that warning first. Once the stream has ended and the archive is available, check Studio separately for a post-stream claim. A warning does not by itself tell you what claimant or segment will appear in an archived claim record, and the later archive check does not undo an interruption that already happened.
The partner-only live matching feature is also not the ordinary Creator Studio path described above. YouTube documents it for certain Content Manager partners; it compares live streams and can warn before interruption or termination, but it creates no claims. Unless you are dealing with that specialised arrangement, keep the two tasks separate: respond to the live notice as it happens, then inspect any archive claim after the broadcast.
For channels where a computer is left running to send a repeated video, the operational risk and the Content ID question are still separate. StreamNeo removes the need to keep your own computer on for the broadcast by letting you upload a video and have it continue as a YouTube live stream, but it does not determine rights or identify a claimant; that still belongs to YouTube’s Studio record.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Does the OBS loop tell me which video Content ID matched?
No. OBS controls show what you configured to send, but the claim and claimant details for an archived broadcast are in YouTube Studio. Use the archived video’s claim details and segment information to compare the record with what was playing.
Can I identify a Content ID match while the stream is live?
Not with this archive workflow. YouTube’s normal claim on an archived livestream comes after the broadcast ends if the video is archived; live warnings and interruptions are a separate process. Do not treat the archive steps here as real-time detection.
Where is the claimant name shown?
Open the archived stream’s claim details, then go to Content used → See details. Read the Claimant field together with the claimed-content description and segment details; a name alone may not identify the exact source recording.
What if there are several claimants or segments?
Inspect each entry separately and note its claimant, content description, segment, and any territory information. Separate claims may cover different portions or vary by region, so do not assume one entry explains the whole archive.