videoslocal.store engine · checking

Practice

A backup routine for the videos you own

Every creator eventually meets the same afternoon: the account is gone, or the phone with the only original is gone, or the platform quietly changed what it keeps. The work was never on the platform. It was on a laptop in 2021, and that laptop has since been sold. This is the routine that prevents that afternoon — deliberately boring, four times a year, and short enough that you will actually do it.

1. Treat the platform as distribution, not storage

An upload is a copy the platform controls. It is re-encoded to whatever bitrate the platform prefers this year, it can be removed without notice, and it disappears entirely if the account does. None of that is a conspiracy; it is just what a distribution channel is. The same is true of cloud photo libraries and "unlimited" storage plans whose terms change after the launch event.

There is a second, subtler loss: the copy you download back from a platform is the platform's version of your work, not yours. The file that left your editor had a master bitrate, a colour profile and often a different edit. If you only ever re-download, you are archiving a photocopy of a photocopy.

Keep the master you exported. The platform's copy is a distribution artefact, not an archive.

2. Decide what a "video" actually includes

The video file alone is the least interesting part of the record. A complete item is a small bundle:

  • The master file — the highest-quality export you still have, not the upload.
  • Captions — as .srt or .vtt, including translations. Re-transcribing costs money; captions are cheap to keep.
  • Thumbnail and cover art — at the resolution you designed, not the platform's 720px squeeze.
  • Description, credits, links — the text that made the video findable and the people who made it credited.
  • Provenance — upload date, platform, video id, and the licence terms you published under.

A plain-text file beside the video covers the last point in about six lines. Future-you will not remember which year the series started.

3. Three copies, two kinds of media, one off-site

The old 3-2-1 rule survives because it is cheap: three copies, on at least two kinds of storage, with one somewhere that burns down separately from your desk. In practice, for a working creator, that looks like a working drive, a second drive kept elsewhere, and an object-storage bucket or a friend's NAS.

The most common mistake is not a lack of drives — it is a lack of supervision. A drive that is never mounted is not a backup; it is a rumour. Put a reminder in the calendar, mount it, copy, unmount.

4. Name files so they sort themselves

Filenames are the cheapest database you will ever maintain. A stable pattern pays for itself the first time you need to find one clip in a folder of four hundred:

2026-11-19_kitchen-table-ep12_yt-aqzKEbpKQ_1080p.mp4

Date first — lexicographic order becomes chronological order. Then a human slug, then platform and id so the source is always recoverable, then the resolution. No spaces, no "final_v2".

5. Put it on a calendar, not on a mood

Four dates a year is enough for most publishing schedules:

  1. Monthly — export new uploads from every platform you published to. Fifteen minutes.
  2. Quarterly — audit the folder: anything published but not archived, anything archived twice, anything whose captions are missing.
  3. Before any rebrand or move — full export, including the old profile text. Handles and bios are part of the record.
  4. Yearly — copy the whole archive to the off-site location and verify it there.

Also export when a platform announces a shutdown, a merger, or a change to its API. Announcements are the only warning you get.

6. Verify, or you have hope rather than a backup

Two checks take minutes and catch almost every failure:

  • Checksums. Generate a SHA-256 for each master and keep the list with the archive. A checksum proves the file on the far drive is the file you made, not a truncated copy from an interrupted transfer.
  • A play test. One file per batch, on a machine that is not the one that made it. Codec support moves; a file that opens today may not open after your next OS upgrade.
The part everyone skips Restore something. Not a test file — a real one, from the off-site copy, onto a clean machine, once a year. A backup you have never restored from is an assumption with a filename.

7. The short version

Master files, not platform re-encodes. Captions and thumbnails beside them. Dates first in the filename. Three copies, one of them elsewhere. A quarterly audit, a yearly restore. It is not glamorous, and that is the point: the routine is supposed to be forgettable, so that losing an account is an inconvenience rather than an ending.

If your work also lives on a platform you no longer trust to keep it, the desk on the front page will pull your own uploads back down so you can fold them into the same archive.