Creator Guide 3 of 4
Preparing
i.Production Requirements
Confirm accepted format, physical size, pixels, profile, compression, background, naming, and any separate path or source file before delivery.
A useful production handoff names the product and revision and makes five checks explicit: where the image goes, how large it prints, how color is interpreted, whether the background should print, and what extra file or approval is required.
Handoff packet
- Approved JPEG and editable source location
- Product template and intended physical dimensions
- Crop and safe-area approval
- Color profile or color-workflow instruction
- Background intent
- Companion file if a path, layout, or other geometry is required
- Named maker or production method and proof expectations
ii.File Organization
Keep editable source, approved export, reference mockup, product template, and proof in separate labeled locations. Do not overwrite the master with a compressed derivative.
Organize source, product-specific exports, listing images, and proof records separately. A common failure is to send the marketplace hero image when the maker expects full-resolution artwork. Version and label each file so the order references an exact approved derivative.
For a simple project, use a source folder, an exports folder organized by product, and a proof or approval folder. Keep listing photos separate from maker production assets, even if both are JPEGs. Record which derivative is attached to the live listing and which revision was approved for an order. This makes a correction possible without guessing among similarly named files.
iii.Naming Conventions
Use descriptive, versioned names such as photo-print-10x8-v2.jpg. Avoid calling a preview the production master, and identify the product and approved revision.
Use a predictable pattern such as project-product-size-orientation-version.jpg, then keep the name short enough for production software. The name is a clue, not the source of truth; dimensions and profile must still be inspected inside the actual file.
An example name might be trail-photo-mug-wrap-v03.jpg. That identifies the design, product, and version without assuming that the filename itself proves size or quality. If a maker needs a specific internal job code, include it in the handoff record or name according to their documented convention. Avoid special characters that the receiving application may reject, and never overwrite an accepted version silently.
iv.Export Requirements
Export at the agreed dimensions, crop, and color settings. Include the profile if required, inspect the saved file itself, and make a new export from the source rather than repeatedly reopening and recompressing an older JPEG.
Export from the source after final crop and retouching. Choose a quality setting by visual comparison, not a universal number. Decide whether to preserve profile and metadata according to the handoff; stripping metadata can remove useful orientation or provenance, while retaining it may expose location information in a public image. Treat listing and private production exports separately.
v.Quality Checks
Check orientation, pixel dimensions, expected background, sharpness, text, gradients, compression artifacts, embedded profile, and the exact displayed or physical size.
Open the exact uploaded or delivered derivative, not only the editor's unsaved preview. Check the file at 100% for compression artifacts and at the final output size for legibility and crop. Inspect corners and edges where trimming and wraps reveal mistakes.
Check Pass condition Pixels Meet the maker's stated effective-size requirement after crop Composition Subject stays inside the product safe area Background Opaque pixels are intentional Color Profile decision is documented and proof is acceptable when needed File integrity Saved file opens in the receiving workflow Version The uploaded file matches the approved revision
