A file manifest is an inventory of the files in a delivery. It helps a recipient check what arrived, identify the intended master, and notice missing items. Include one when you use FileFlap to deliver a package with many folders or important production assets.
Decide what the inventory should contain
Start with each file's relative path, size, and purpose. Relative paths describe locations inside the delivery, such as Masters/Interview_v03.wav, without exposing folders on your own computer. Record sizes in bytes when exact comparison matters, because rounded megabyte values can hide differences.
Add a version or release identifier at the top. Optional fields include format, language, status, and a SHA-256 checksum. Only include fields you can keep accurate; a complicated spreadsheet that is out of date creates more confusion than a simple verified list.
Use a readable format
A CSV works well for inventories that recipients may sort or filter. A plain-text README can explain the package and point to the inventory. Use explicit column headings such as relative_path, size_bytes, and purpose. If filenames contain commas, ensure your CSV tool quotes them correctly.
For example, a row might describe Masters/Film_v03.mov as the approved video master, while Review/Film_v03_small.mp4 is a smaller review copy. The distinction prevents a convenient preview from being mistaken for the production deliverable.
Generate the manifest after the package is final
- Collect the intended files in a delivery folder.
- Remove temporary files and superseded outputs.
- Inventory the final paths and file sizes.
- Calculate checksums if the handoff needs integrity verification.
- Recheck the inventory after any change to the package.
Explain whether the manifest lists itself and whether checksums apply to extracted files or the outer archive. Avoid a circular requirement to embed an archive's own checksum inside that same archive; put the archive checksum in an accompanying message or separate file.
Tell the recipient how to use it
Send the download link with the release name, expected file count, and location of the manifest. Ask the recipient to extract the package, compare paths and sizes, and report specific missing entries. Matching checksums can confirm matching bytes, but a checksum supplied alongside an untrusted file does not by itself establish who created it.
Does every small transfer need a manifest?
No. A clear message may be enough for one document. A manifest becomes useful when file counts, nested folders, multiple versions, or the cost of a missing asset make informal checking unreliable.
Choosing a service for your next delivery? Our WeTransfer alternative guide starts with FileFlap and explains the delivery features to compare.
← All articles