ItemlumePRODUCT CREATIVE / PRODUCTION AND HANDOFF
Why does my Lottie product animation move on the new site but its product photo is missing?
When the motion plays but its product photograph is absent, check whether the animation and image assets traveled separately. An externally linked JSON file may need accompanying images. Establish the export strategy and deployed resource paths before rebuilding the composition; the symptom alone does not prove a missing file.
1. Separate missing image assets from animation failures
Illustrative exercise: the fictional bottle promotion below is a proposed investigation, not an executed After Effects, Creator, export, upload or player test.
Imagine a skincare promotion where a bottle photograph slides into a moving frame beside a discount message. On the designer's computer, everything appears complete. On the storefront, the frame moves but the bottle disappears. The important clue is that some animation behavior remains visible while one particular visual asset is missing. This suggests checking the image handoff before rebuilding the composition.
LottieFiles documents two image-handling approaches for its After Effects export workflow. Images may be embedded as Base64 data within JSON, or exported separately and referenced by the animation. The second approach requires the associated image files to accompany the animation. A linked JSON file alone is therefore not necessarily a complete delivery package.
Do not diagnose solely from appearance. An incorrect reference, omitted deployment asset, unsupported rendering behavior, or another integration problem may produce a similar symptom. First establish whether the expected image exists in the exported deliverable.
2. Choose an image delivery contract before exporting
Branch A — Portable brand animation: A small campaign badge contains a modest photographic element and must pass between agencies without a separate asset folder. Evaluate embedding the image into JSON. The acceptance requirement is a self-contained handoff, not an assumed performance advantage. Review the resulting file size against the site's actual constraints before approving this route.
Branch B — Photographic product sequence: A merchant maintains several product photographs as separately managed assets. External image references may fit the workflow better, provided the team delivers the complete image set and agrees on the published paths. Sharing the same photograph across creative versions does not excuse missing files or unresolved references.
Neither branch turns a PNG or JPEG photograph into vector paths. Raster photography is legitimate content when its appearance is intentional. If the team instead packages an animation as .lottie, confirm that the actual container and destination runtime support the intended delivery; renaming a JSON file cannot repair missing resources.
3. Document the intended After Effects export route
For the documented LottieFiles After Effects plugin workflow, open Window > Extensions > LottieFiles, select Export, locate the relevant composition, and open Render Settings. Under Assets, review the intended image strategy. Current controls include embedding image assets in JSON, keeping original asset names, copying original assets, and skipping unchanged image exports.
Record the chosen settings and the deliverables expected from that configuration. If external files are required, name the files and their destination directories in the handoff manifest. Do not substitute an arbitrary JSON edit for checking the actual export and asset references.
Treat skip-unchanged behavior as an export-workflow option, not evidence that every necessary image has reached the recipient. A designer's local cache, previous export directory, or existing image copy cannot establish that a new storefront deployment contains the complete asset set.
4. Propose a clean-environment acceptance check
Ask the developer to stage the delivered files in a fresh directory without relying on the designer's working folders. For linked assets, compare the referenced locations against the files actually supplied. Then propose a separate check on the intended deployed page, using its real published asset paths.
The reviewer should inspect the bottle photograph, crop, orientation, transparency where applicable, and the timing of its appearance. Compare those observations with an approved product reference. Motion playing correctly does not establish that the correct product photograph was delivered.
Record each discrepancy as missing file, unresolved reference, unexpected visual content, or undetermined. Keep an unresolved result open until the actual target environment has been inspected. No clean-folder, deployed-site, or player test has been performed for this guide.
Product Photo Delivery Decision and Acceptance Worksheet
These are illustrative exercise rows. Save a copy and record your own observations; the example is not an executed acceptance test.
| Branch | Merchant scenario | Image strategy | Required handoff evidence | Proposed acceptance check | Decision status |
|---|---|---|---|---|---|
| A | Portable seasonal brand badge with one product image | Evaluate embedded Base64 image | Exported JSON and recorded Assets configuration | Open from a fresh delivery location and inspect the approved photograph | Illustrative exercise — not tested |
| B | Photographic product sequence with separately managed images | External linked image assets | JSON, complete image manifest, asset files, and intended published paths | Check deployed references and compare each displayed product photograph | Illustrative exercise — not tested |
Sources and further reading
Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.
Frequently asked questions
Does a moving frame prove that the missing photograph was not exported?
No. It only establishes that some animation content is displaying. Inspect the exported image strategy, available asset files, and published references before deciding where the photograph was lost.
Should every product photograph be embedded to prevent missing assets?
Not automatically. Embedding can simplify a portable handoff, while external files may suit separately managed photographic content. Choose using actual deployment requirements, file inspection, and agreed acceptance criteria.
PREPARE ASSETS FOR YOUR NEXT STEP
Create supporting product assets in Itemlume.
Create new product creative assets in the workspace, then continue in your chosen tools. Third-party software procedures described in this guide take place in those applications; this workspace link does not imply an integration. Check current capabilities, account access and credit quotes.
Explore asset creation tools Check pricing and credits