Skip to content
Pet Studio journal

Pixel Pet Version Handoff: Keep Names, Previews, and Exports Straight

A practical handoff record for pixel pet versions: confirm the name source, label the approved preview, and name every export so nothing gets mixed up.

A pixel pet handoff can fail without any art error: three files arrive as final.png, final-final.png, and preview.png, and nobody can tell which one carries the owner’s spelling of the pet’s name or which export has transparency. The fix is a small handoff record that travels with the files, not a longer folder.

Anchor the handoff to one canonical record

Name source

Use the name exactly as the owner supplied it in the brief or approval message. Record where it came from: “owner email, 12 May” or “order form field.” Do not infer the name from the photo filename, breed, or a previous pet. Keep a display name (Mochi) and a file slug (mochi) separate. If the owner has not confirmed spelling, mark the handoff name-pending and do not publish a named export.

Preview with a job

The preview is for approval, not delivery. Name it with the same slug and version, and put the version and the word PREVIEW inside the image so a screenshot cannot be mistaken for a final asset. Show the pet at a readable size on a neutral background. Keep one approved preview per version; do not let a newer preview overwrite the one the owner approved. For pixel edges, crisp PNG preview guidance matters more than a large canvas.

Exported variants

List every export in the manifest before generating files. Each row needs: variant purpose, dimensions, background (transparent or solid), animation state if any, and approval status. Filenames should repeat the slug, version, variant, size, and alpha state, e.g. mochi_v03_transparent_64.png. Never use final as a version. If a variant is not approved, label it review and keep it out of the delivery folder. Before delivery, run the transparent edge halo check on the alpha variants.

Worked example: Mochi v3

Inputs: the owner writes “Mochi,” supplies photo IMG_4821.HEIC, and approves pose v3. The handoff needs three image files: a 64×64 transparent sprite, a 256×256 transparent sprite, and a 512×512 preview on dark gray.

Outcome:

  • mochi_v03_preview_512_dark.png — approved preview, version label visible.
  • mochi_v03_transparent_64.png — game export.
  • mochi_v03_transparent_256.png — store export.
  • mochi_v03_handoff.md — name source, source photo reference, approval date, variant table.

Instructions:

  1. Copy the owner’s spelling into the manifest before opening the art file.
  2. Assign v03; do not reuse v02 even if only the background changed.
  3. Generate each export from the approved source, then check dimensions and alpha against the table.
  4. Put previews and exports in separate folders.
  5. Send the manifest with the folder, not after it.

The constraint that changes the action

If the owner’s name confirmation is missing, stop at the preview. Do not create “probably right” named exports, because a wrong name propagates into filenames, store listings, and future versions. Hold the package as name-pending, send the preview for confirmation, and only then generate the export set.

Sources and boundaries

This editorial note is provided for education and creative inspiration. Product terms and availability may change.

Last reviewed .

Custom Codex & ChatGPT Pets from Your Photo

Pet Studio creates a downloadable artifact; it does not claim ownership of third-party agent products or guarantee compatibility beyond the exported format.