Keep a small approval record that connects the original source, the generation task and the selected output. A library thumbnail alone does not tell you which version a person approved. Before publishing or sending a file to a printer, open the actual exported asset and compare it with that record.
Give each creative purpose its own selection
An image can be approved as a photocard but unsuitable for a circular badge. A video can be the accepted wide-format shot while a separate vertical crop remains unfinished. Record approval for the intended use, not as a blanket statement that the asset is correct everywhere.
Use the website's available workflow categories to find likely files, then verify the individual task. Keep your own short note when the interface does not provide a dedicated approval control. This guide does not assume that shared folders, custom tags or team sign-off are built-in features.
Use a four-part handoff record
| Item | What to record | Why it helps |
|---|---|---|
| Source | Authorized input or reference identifier | Explains which identity or scene was intended |
| Task | Job ID and creation workflow | Makes the generation traceable |
| Selection | Exact accepted file and revision | Prevents a thumbnail-based guess |
| Use | Placement, crop and reviewer | Defines what the approval actually covers |
You do not need to place personal information in filenames. A project label, format and revision can be sufficient. Keep sensitive reference records in an appropriate private location rather than turning a public download name into a biography.
Compare the final file, not only the preview
Example acceptance note: project Greenhouse, ceremony shot 04, selected take B, landscape delivery. Approved for the first edit after checking both faces, the closed box and the complete movement. The vertical crop and soundtrack are not yet approved. Downloaded filename and job ID are recorded together.
This is a manual production note. Replace its details with what you actually reviewed. A thumbnail can conceal an incorrect frame, a broken download, unintended audio or a resolution different from the expected output.
For images, check dimensions, format and the final crop. For video, play through the beginning, middle and ending and listen to the soundtrack. If the file cannot be opened independently, it is not ready for handoff merely because a preview appears on the website.
Keep working candidates separate from deliverables
Maintain an approved delivery folder in your own storage and a separate working area for alternatives. Download important accepted assets in time rather than treating any online library as an unlimited archive. Use the retention information currently shown by the service; do not infer a permanent-storage promise from a visible thumbnail.
Use Imagild Library and Jobs together: one helps locate assets, the other provides task context. Neither replaces the final editorial decision about which result is suitable for publication.
Should I delete every rejected version immediately?
Not necessarily. A rejected candidate can help explain a correction. Keep only what is useful under your own storage and privacy practices, and avoid deleting the sole approved file by mistake.
Does a completed job mean the content is approved?
No. Completed describes processing. Approval describes a human decision about identity, content, quality and intended use. Keep those two states distinct.