Source: https://restorebunny.com/guides/write-a-photo-archive-readme/ # Write a README for a Family Photo Archive Explain folder structure, naming, restrictions and recovery contacts in a portable archive README. Digital organization2 min readUpdated 16 October 2026 ## Try it on your own photo Repair a copy of your photo, then compare faces and details with the original. [Restore my photo]()1 credit per successful photo · Account required[See credit packs]() Quick answer ## The short version A README gives the next person an entry point into your archive. Write it as if the reader has never used your computer. Explain where originals live, which files are derivatives, what identifiers mean and how restrictions are recorded. Keep recovery arrangements practical without storing account secrets in the document. ## Define the job before editing A README gives the next person an entry point into your archive. Write it as if the reader has never used your computer. Explain where originals live, which files are derivatives, what identifiers mean and how restrictions are recorded. Keep recovery arrangements practical without storing account secrets in the document. ## Explain the exceptions as well as the rule Describe the top-level folders, date conventions and unknown-date labels. List unusual file formats and the inventory filename. Explain why a few items are in restricted storage or why two versions have competing identifications. Give a custodian contact and a separate process for obtaining credentials. ## Make the decision from evidence Prefer plain text or another easily opened document alongside any richly formatted copy. Do not rely on an application’s help panel as the only explanation. Test the README by asking a trusted relative to locate one original and one approved sharing copy using only its instructions. ## A worked planning example Example: The README says masters are in 01-originals, working edits in 02-edits and approved copies in 03-share. Dates ending in -approx are estimates. A named custodian holds the backup map; no passwords appear in the archive folder. ## A practical checklist 1. Describe the folder structure. 2. Explain IDs and uncertain dates. 3. Point to the inventory and access notes. 4. Ask another person to follow the document. ## Keep a traceable result Keep the source file, the working copy and the delivery copy as separate items. Record the input and the changes you actually made so another person can understand the result later. These workflow examples are planning examples, not documented customer outcomes or proof of a successful restoration. ## FAQs Should the README include cloud account passwords? Keep passwords and recovery codes in an appropriate separate security process. The README can identify who manages access without exposing credentials. Should I replace my original with the edited copy? Keep the source unchanged and save a separate working or sharing copy. An export, edit or AI interpretation can omit information that remains useful in the source. ## Sources Preservation and technical guidance reviewed for this article. - Library of Congress: [Personal archiving: digital photographs]() ## Related - [Open the related free tool]() - [Move a Photo Archive to a New Drive with Checksums]() - [Divide a Shared Family Photo Archive Without Losing Context]() - [Browse photo guides]() - [Free image tools]() ## Ready to restore your photos? Upload an image, choose your settings, and preview results with a before/after slider. [Restore my photo]()[View Pricing]() RestoreBunny Source-backed photo workflows Guides follow our [editorial policy]() for sourcing, product claims, AI limitations, updates, and corrections.