A useful project folder should make sense when you return to it later. Start with a small structure and add detail only when it helps you find something. For a collection of images, a few clearly named folders and a short README are often enough.
Separate sources from exports
field-project/
sources/
exports/
README.txtKeep downloaded artwork and editable originals in sources. Put files prepared for a particular destination in exports. Give the exports descriptive names, such as cover-1200w.webp or palette-web.css, rather than a sequence of “final” filenames.
Write a short handoff note
A README can say what the collection contains, where the source material came from, which exports are intended for use, and which licence applies. Include any important dimensions or colour choices. Avoid putting passwords, access tokens, or private account details in a file that may be shared.
Check a finished archive
Open the archive after creating it and inspect its contents. Confirm that the intended exports are included and that you have left out unrelated material. A file checksum can help compare the archive with another copy later, but it will not tell you whether you packaged the correct files.
For a small handoff, record the archive’s name and SHA-256 in a separate note. Keep the editable source folder as well. An archive is a delivery copy, not a substitute for a source you can continue working on.