An archive starts with a purpose
A channel is a publishing destination, not a complete production archive. A creator may need an offline copy before travelling, when moving between editing tools, or when a client asks for an older approved cut. Those are different needs. A viewing copy should play reliably. An editing archive should preserve the highest-quality original you still possess. A client delivery should match the version they approved. Deciding which one you are making prevents an unnecessary download from becoming a misleading “master”.
This workflow is for videos you own or are authorised to retain. Keep the permission or commission agreement with the project. A public page does not itself establish a right to copy the work, and a tool finding a downloadable source does not settle ownership.
Keep the original when you have it
Start by looking in the camera archive, editing project and export folder. An online platform may create different resolutions and codecs from your upload. Downloading a 1080p version of a 1080p upload does not prove that the two files have identical compression or detail. If you still have the approved original export, keep it as your master and treat the website copy as an additional viewing or recovery version.
When the original is missing, record that fact honestly. A recovered publication copy can be useful without becoming a replacement for footage that no longer exists. Do not label an upscaled image or a converted audio file as a higher-quality original.
Make a short manifest before downloading
Create a simple project note containing the title, source page, publication date if known, intended use and permission basis. Add the intended destination folder and the device that must play the result. For a client project, include a version identifier rather than relying on a title such as “final final”. A spreadsheet or text file is enough; the important part is that someone else can understand the archive later.
Avoid putting private access tokens, account passwords or confidential source links in a shared manifest. If the source requires a private login that FIRST does not support, return to the platform’s authorised export route instead of trying to work around access restrictions.
Choose the available format for the job
In FIRST’s website workflow, paste the individual video URL and inspect its available formats. Video choices and file sizes depend on the source. MP4 is often a practical viewing choice because FIRST’s MP4 profiles use H.264 video with AAC audio. WebM may be offered when that source is available. A larger resolution can help for a large display, but it can also increase transfer time and storage requirements.
Use the measured or estimated size to make a storage decision, not as proof of quality. A sample-based estimate is marked as approximate. Website output is currently limited to 2 GB; choose a smaller available source if necessary. The three-download trial counts successful transfers, not minutes, so a video over an hour still uses one slot.
Allow time for preparation and saving
The website prepares the media on a server, then gives you a file to save through the browser. It is a different workflow from FIRST’s optional desktop extension, which can process supported sources locally with a companion. A phone does not need that extension for the website route. Keep the page open while preparation runs, and wait for the Save to my device link before assuming that the file is yours.
Prepared files are temporary rather than a storage locker. Save the file while its link remains available. A progress indicator reaching its end describes server preparation; it does not establish that your browser has finished writing the file to local storage.
Verify the actual file
Open the saved file from the destination folder, not from the source website. Check the beginning, a middle section and the ending. Listen for the intended audio track. Look for a sensible duration and confirm that the file plays in the software your recipient will use. An MP4 suffix describes a container; it is not, on its own, a guarantee that every player will support every codec someone might place inside it.
For an important archive, record the file size and a checksum using your usual file-management tools. A checksum helps identify accidental changes later; it does not establish copyright ownership or prove that the platform copy equals your original export.
Name and organise the archive
Use a consistent naming pattern such as project, version, date and format. Keep a small README next to the files explaining which copy is the publication recovery and which is the production master. Place captions, artwork, releases and project files in clearly named folders. FIRST downloads do not automatically create transcripts, rights records or editable project timelines.
Maintain another backup on a separate storage device or a backup service you control. Do not rely on a phone’s only local copy or on FIRST’s temporary server link. If an archive contains personal or client information, control who can access it and review any retention commitments you made to the people involved.
A useful completion check
Your archive is ready when the intended device can play the saved file offline, the version is identifiable and the permission record is easy to find. If any of those checks fails, resolve it before deleting an older copy. A short test now is much easier than discovering an audio problem at a presentation.
For repeat work, make this a checklist rather than a memory exercise: confirm rights, locate the best original, inspect available formats, save, play, document and back up. The result is a collection that can be trusted for its stated purpose, even when the only recoverable file is a platform’s viewing version.