ChatGPT
Claude
Useful image file naming conventions separate three things: what the image is, which revision it represents and which delivery copy you are holding. Choose a short consistent pattern, keep the original download, and record how each crop or web export relates to its source. A name should help someone identify a file without pretending to carry its entire approval history.
This guide is for a creator handing generated images to another designer, publisher or developer. It covers file identity and image derivatives. It does not require a coding agent, a digital asset management purchase or a new automation system. The filenames and example project below are invented, reusable planning examples.
Start with the decisions people actually make
Imagine a folder containing an original image, an approved retouch, a square crop and two web exports. If every file is called final, the publisher has to open each one to reconstruct the work.
Before choosing a pattern, identify the questions the next person must answer:
- Which image or subject is this?
- Is it a new creative revision or another export of the same revision?
- What crop or pixel dimensions does this copy contain?
- Where is the source and where is its approval recorded?
- Does this filename already exist at the destination?
Avoid encoding every possible fact. Prompt text, private client details, model settings, generation identifiers and review discussions can live in a separate record. A filename that tries to include all of them becomes difficult to scan and easy to truncate.
Choose one compact pattern
An adaptable pattern is:
subject-or-purpose-revision-derivative.extension
For a fictional bag image, that might become:
| File | Meaning |
|---|---|
| harbor-bag-desk-r01-source.png | First selected source revision |
| harbor-bag-desk-r02-master.png | Revised editable image represented by this export |
| harbor-bag-desk-r02-square-1080.webp | Square delivery copy derived from revision two |
| harbor-bag-desk-r02-wide-1600.webp | Wide delivery copy from the same revision |
The pattern is a proposal, not a universal standard. Use the conventions already required by your repository, image library or client. Queen's image guidance, for example, sets institution-specific naming and version rules and warns against renaming originals obtained from its asset bank. That illustrates why local retention requirements come before a generic template.
Use a consistent separator and case. Write a short note explaining what r02 means and which derivative labels are allowed. If two people interpret the same field differently, the pattern has not solved the handoff problem.
Distinguish revisions from derivatives
A new creative revision changes the accepted picture: perhaps the background, product placement or illustration. A derivative changes how that revision is delivered: a crop, size or approved format conversion.
If you darken the background after producing the square crop, decide whether that is a new revision and regenerate the affected derivatives from the accepted master. Otherwise the wide and square files may appear to belong together while showing different artwork.
Keep a small mapping record:
Asset: harbor-bag-desk
Accepted revision: r02
Source file: preserved original download
Master: harbor-bag-desk-r02-master.png
Delivery copies: square-1080.webp, wide-1600.webp
Approval: named reviewer and recorded decision
Destinations: exact page or handoff location
A filename containing approved is not evidence that someone approved it. Keep the actual decision attached to the revision. Do not silently overwrite the master merely because a later generated option looks attractive.
Keep public image names descriptive
Google's image guidance recommends concise descriptive filenames and says they provide a small clue about image subject matter. It does not justify filling a filename with repeated keywords or promising a ranking improvement.
Use a meaningful public name rather than an opaque download label when the publishing workflow permits it. Keep extensions consistent with the actual file type. Renaming a PNG extension to WebP does not convert its bytes; use a real export or conversion step and inspect the result.
Keep the public name free of credentials, customer details and private internal notes. A publicly served filename can be visible in a page's markup or URL even when it never appears as a caption.
Handle an existing live filename carefully
For a new unpublished image, selecting a name is usually straightforward. For a file already referenced by a website, renaming becomes an integration change. Record the consuming pages and have the publisher update the references using the project's normal process.
Do not rename a live image just to make the folder prettier. Check whether the benefit warrants changing its URL, markup and any related records. If the system deliberately keeps a stable public filename while versioning sources elsewhere, follow that contract and preserve a mapping to the exact deployed bytes.
This is different from choosing test identifiers for an ad campaign. The agency variation workflow covers hook, scene and CTA naming across many ads. The Codex image workflow covers repository placement and generation records. Use this article for the source-versus-revision-versus-derivative decision that applies even without either workflow.
Test the naming rule before using it everywhere
Try it on one small asset family. Ask another person to identify the source, latest accepted revision and exact delivery copy without your explanation. If they cannot, shorten or clarify the rule before renaming a large library.
Check for collisions, accidental duplicate extensions and derivatives claiming dimensions they do not actually contain. Open the final export and verify its properties. A label such as square-1080 is a statement to verify, not a resizing operation.
Keep originals and old decisions according to your existing retention policy. If the next generation is a replacement rather than another derivative, give it an explicit new revision and retain the relationship.
Generate a source image in Oakgen, then organize the downloaded image within your own file workflow. Oakgen is not being described as automatically applying this naming pattern to your folders or website. Create an account if needed and check the displayed quote before generation; no free-generation allowance is promised.
