How should you organise nature images across a project? – Cheap Nature Images

Nothing here is required by the licence. It is what makes the licence provable a year later, which is when someone always asks.

Keep the asset id

Every image has a thirty-two character asset id. It is in the file metadata, on the receipt, and in the image page source. Titles change and slugs change; the asset id does not.

If you record one thing, record this.

A three-column log

A spreadsheet is sufficient. Asset id, PayPal order id, and where the image was used.

That is the entire compliance system. When a client, a printer or a legal review asks whether the picture on page four is cleared, you answer in ten seconds instead of spending an afternoon reconstructing it from email.

Folder discipline

Keep originals separate from derived files, and never edit an original in place.

project/
  images/
    originals/     as downloaded, never touched
    working/       layered files
    export/        derived, web and print

Re-downloading only works inside the seven-day window. An original you deleted is an original you will be writing an email about.

Naming

Keep the asset id in the filename. a3f1…-valley-fog-hero.jpg is far more useful than hero-final-v3-FINAL.jpg, and it survives being moved between machines and handed to a contractor.

Metadata

The IPTC fields travel with the file: title, description, keywords, asset id. Most layout applications read them and many asset managers index them. If you use a DAM, ingesting those fields means the log above builds itself.

Handover

When a project ends and you hand it to a client, hand over the log, not the original files. The layouts are theirs; the licences are yours, and passing the originals along is the one thing the licence does not permit.

If the client needs the originals, they buy their own licences. At three dollars this is a line item nobody has ever argued about, and it makes the boundary explicit for both sides.

Backups

Treat licensed originals as project source, not as cache. They belong in whatever backup covers your working files, because the seven-day download window is not a backup and neither is your downloads folder.

The cheapest version of this is a single archive folder per project, copied wherever your other project source goes. It takes no discipline beyond doing it once at the start, and it removes the one failure mode that actually costs money: rebuilding a layout because the original is gone.