Public-domain footage for YouTube: a dated source-review checklist

Finding footage in an archive is a starting point for research, not a complete reuse decision. Preserve the source page, the specific file, the rights statement you observed, attribution details and the date checked. If something remains uncertain, mark it unverified before publication rather than allowing a convincing edit to make the question disappear.

This is an editorial recordkeeping workflow, not a determination that a particular file or planned use is permitted. It includes a practical checklist for material found through NASA, Wikimedia Commons and the U.S. National Archives. Read the original institution’s guidance and resolve asset-specific questions; a source-credit generator cannot clear rights for you.

Separate five questions before downloading

First ask what the material actually depicts. A properly documented photograph of one mission can still be the wrong visual for a statement about another. Next establish where the file comes from and whether the description identifies a creator or contributor. These are factual research questions before they are reuse questions.

Then record the rights statement as stated, rather than translating it into a broader promise. Identify any attribution, change-notice or other requirements that need review. Finally, consider the intended use and relevant jurisdiction. A label observed on a page is evidence about that page, not a universal verdict on every way the material might be used.

Keep the answers separate in your working record. If the image is historically appropriate but the rights information is incomplete, one successful check must not overwrite the unresolved one. Likewise, a detailed license description does not prove that the subject identification is correct.

What a check date does and does not mean

A check date identifies when a reviewer observed information. It is useful because pages, downloadable versions and attributions can change. It does not mean the reviewer obtained a legal guarantee, and it should never be displayed as a substitute for the statement being reviewed.

Use a clear date format and record the page location. For a changed project, preserve the earlier observation and add the new one rather than rewriting history. If an editor cannot tell which file was checked, a date alone has little practical value. Tie it to an asset identifier and the shot or version that used it.

A later date is not automatically a better record. The quality of the observation matters: which page was opened, which passage was recorded, which file was downloaded and which questions remained open. “Checked today” without that context is difficult for another person to evaluate.

NASA: read the current guidance before making assumptions

NASA publishes images and media guidance covering use conditions and important limitations. Check the original guidance and the specific asset’s credits, including whether material is supplied by another rights holder. Do not turn “found on a NASA page” into an unrestricted commercial-use promise.

For your project record, write down the asset’s exact caption and credit, the file identifier and the page used for the observation. Keep any unresolved branding, endorsement, people or third-party-material questions visible for appropriate review. This article does not decide those questions for your particular video.

Treat a scene’s historical meaning independently. An image can be accurately credited yet imply the wrong date, operation or personnel when cut beside a sentence. Include a short note explaining whether the visual is direct evidence, contextual background or an illustration of a concept.

Wikimedia Commons: inspect the individual file description

Commons’ reuse guidance explains that files can have different requirements. Inspect the actual file-description page and linked license rather than relying on a search-result thumbnail or a generic statement about the collection. Preserve the creator credit and any required notice for changes.

A download URL alone often omits useful context. Keep the description-page URL as well as a local identifier for the downloaded file. If multiple versions exist, note which version your editor received. If statements conflict or a requirement is unclear, record the conflict and pause the affected shot’s approval.

Do not assume the uploader and creator are always the same person. Record the labels actually presented and avoid inventing missing fields. An unknown creator should not become “Wikimedia” merely because that is where the file was found. A formatter should preserve uncertainty rather than silently normalizing it away.

National Archives: use catalogue context, then verify restrictions

The National Archives can be a research starting point for historical moving images. This draft does not assert that a particular catalogue entry is reusable: the research fetch of the proposed film reference was unavailable, so its asset-level conditions remain unverified here. Start from the National Archives website and locate the actual record and restrictions information before choosing a file.

For a production record, preserve the catalogue identifier, description, item or reel reference, available rights/restrictions notes and the location of the passage you checked. If only a collection-level description is available, do not pretend it is an item-level clearance. Ask the relevant archive or obtain appropriate advice when the intended use depends on unresolved information.

A working record your editor can actually use

The following is a template, not a cleared asset. Blank or unresolved fields must remain visible. It is deliberately broader than a credit line because an editor needs to know what to check, not only what to paste into a description.

Keep the intended use alongside this table. An image chosen for an educational explanation and the same image chosen to imply an endorsement can raise different questions. Do not let a reusable spreadsheet category decide a use the reviewer never saw.

Worked example: preserve an unresolved record

Imagine a fictional production about a bridge. An editor finds a photograph titled “River crossing” on a collection page. The date is uncertain, the creator field is incomplete and no linked terms have been checked. This is not a real asset recommendation; it illustrates how to avoid manufacturing certainty.

Create ARCH-014 and mark it unverified. Record the collection page and the caption exactly as observed, note which details are missing and leave the shot out of the approved export set. The editor can keep it as a research lead while seeking a better-documented alternative.

If another photograph later replaces it, create a new record or a new version with the new file identifier. Do not change ARCH-014’s creator field to the replacement’s name and leave the old source URL in place. That would produce a tidy-looking table with a misleading history.

When the brief changes, revisit the record. A contextual image used behind a broad explanation may be reconsidered if the narration now names an exact event. Review states should describe the actual approved use, not merely the fact that someone once looked at the file.

From a source record to a YouTube credit draft

The source attribution builder accepts supplied fields and formats them into readable text. Its walkthrough uses a synthetic example so you can check the output without confusing an example with approved media.

The tool does not visit URLs, interpret license terms or establish commercial permission. Keep your check date and review status in the underlying asset record even when the short credit draft does not display every internal field. Before publication, compare the draft against the original source requirements and the actual material in the edit.

A description should be useful to a viewer, but it is not the only evidence you keep. Preserve the full record privately with the project’s deliverables. If someone later asks about a scene, you should be able to locate the relevant file and observation without searching every page you opened during research.

Keep factual evidence separate from visual permissions

The document supporting a narrated claim and the record supporting a visual’s use may be different. A mission report can support an engineering statement while a photograph provides context. An attractive image does not prove the causal statement beside it.

Use a claim ledger for factual support and an attribution record for media information. Connect them through the shot and script version, but do not collapse them into one “source checked” box. That separation makes revisions easier to review without claiming the workflow is an automatic fact-checker.

FAQ

Is everything on an archive website public domain?

Do not assume so. Inspect the specific item, creator information and relevant restrictions or terms. Collection access, historical age and a search-engine label are not enough to settle the status of a particular file.

Does attribution make an uncertain use acceptable?

A credit line does not resolve all conditions. Preserve the information and review the actual requirements. If permission or status is still uncertain, keep the material marked and address the question before publication.

How often should records be checked again?

There is no universal interval established here. Review the record when the asset, intended use, source information or project version changes, and define an editorial checkpoint before release. Preserve earlier observations instead of replacing their dates.

Will this checklist prevent claims or guarantee monetization?

No. Records improve traceability, not certainty about every future dispute or platform decision. YouTube controls its own eligibility and policy reviews; no source table promises views, revenue or YPP approval.

Use the record before you polish the film

Start with a small set of well-documented assets and visible open questions. Try the free attribution tool, use the glossary and workflow guides, or request a sample to discuss a brief. Topicut’s self-serve rendering and checkout remain closed; its source records support human review rather than automatic rights clearance.

Related workflow

Keep a production brief with your decisions, and explore the Topicut guides for the next review step. The cover is an original Topicut editorial graphic, not a vendor interface or a measured comparison.