Free studio reference
Product photography quality control checklist
Use this framework to define what the studio checks before product images are approved and released, from product identity and color to technical output, file naming, and delivery.
This is a practical framework created by Lenso. It is not a certification, contract, or universal marketplace standard.
Framework version 2.0Last reviewed: August 20, 2026
Use the current requirement, not a universal default.
A quality-control check is only useful when the reviewer knows what the file is being checked against. For each job, identify the current brief, shot list, style guide, channel requirement, approved reference, and person authorized to make the final decision.
A studio can adopt its own repeatable baseline, but the client agreement and current approved job requirements control the work. Marketplace, retailer, and platform requirements can change and may vary by region, category, account, theme, or use.
When a requirement conflicts with this framework, record the current source, the decision, and the accepted exception rather than treating the framework as authority.
Use it before release, not after a client reports a problem.
- Name the current requirement or source for each check.
- Review the actual files that will be released, not only working files.
- Use an approved reference or physical sample when visual matching matters.
- Record who reviewed the set and who can make the final client decision.
- Write down every accepted exception and the files it affects.
- Reopen the check when the brief, shot list, reference, output specification, or delivery set changes.
- Keep the final review record with the job.
In a solo studio, the same person may produce and review the work. Use a separate, deliberate review pass rather than checking from memory during export.
Quality-control record
- Job:
- Client:
- QC version:
- Review date:
- Reviewer:
- Final client decision maker:
- Current brief or shot-list version:
- Approved reference or physical sample:
- Required channel or destination:
- Accepted exceptions:
- Final release set or manifest:
Record the current source of truth. A file name, URL, document version, or job-history entry is more useful than "same as usual."
Use one clear outcome for every issue.
A failed check does not always mean the same thing. Use one of these labels in the review notes.
- Pass
- The file matches the current requirement.
- Correct before release
- The studio can correct the file without a new client decision.
- Client decision needed
- The current requirement is missing, conflicting, or changed.
- Accepted exception
- The authorized decision maker accepts a documented deviation for the named file or set.
These are operational labels. They do not define legal acceptance or financial responsibility.
Quality-control checklist
Check the final release files against the current approved requirement. Leave an item unchecked when it needs correction, a client decision, or a recorded exception.
Required set and product identity
Confirm that the set represents the right products and includes the outputs the job requires.
Complete when
The studio can identify every final file and explain which approved requirement it satisfies.
Product truth and visible condition
Confirm that editing and presentation do not create a misleading version of the product.
Complete when
The final image remains an accurate representation of the approved product and treatment.
Framing, crop, scale, and composition
Confirm that the image uses the required view and leaves the product visible as intended.
Complete when
The crop and composition match the intended output rather than a remembered default.
Background, edges, shadows, and reflections
Confirm that the product is separated and grounded according to the approved visual treatment.
Complete when
The background and edge treatment match the approved use and remain visually consistent across the set.
Color and retouching
Confirm that color and editing match the approved reference within the agreed review conditions.
Complete when
Color and retouching match the approved visual target without misrepresenting the product.
Technical output
Confirm that each file can be used at the intended destination.
Complete when
The actual exported file matches the technical requirement for its intended use.
File identity and manifest
Confirm that the recipient can identify the file and that the studio can trace it to the correct job context.
Complete when
The recipient can identify the final files and the studio can reconstruct how each one relates to the approved job.
Approval, release, and delivery
Confirm that the right version is released to the right person under the current job rules.
Complete when
The studio can identify what was approved, what was released, who received it, and which exceptions were accepted.
Channel requirements are separate from the studio baseline.
Amazon, Shopify, Google Merchant Center, retailers, marketplaces, and client-owned systems do not share one universal image standard. Requirements can vary by region, category, account, theme, product type, ad format, and use.
Use the official source for the destination and record the version or review date in the job. A client instruction can be stricter than the platform minimum.
The examples below were reviewed against official sources on August 20, 2026. Verify them again before using them for a current job.
Current official channel references
Verify before use
Amazon US Seller Central
Product Image GuideLast reviewed: August 20, 2026
At the time of review, Amazon's US guide says a main image must use a pure white background, show the product at about 85 percent of the frame, avoid text, logos, borders, watermarks, and unrelated props, and show the product once rather than combining front and back in one image. Its technical guide lists a 500 to 10,000 pixel longest-side range and recommends JPEG.
Amazon category, product, program, and regional rules can add or change requirements. Use the current Seller Central source for the exact listing.
Open Amazon's current Product Image Guidehttps://sellercentral.amazon.com/help/hub/reference/external/G1881
Shopify
Product media guidanceLast reviewed: August 20, 2026
At the time of review, Shopify accepts product and collection images up to 5000 x 5000 pixels or 25 megapixels and under 20 MB. Shopify says 2048 x 2048 pixels usually displays best for square product images, while actual display depends on the store theme.
Shopify does not create one universal background, crop, or aspect-ratio rule for every store. The client brand, theme, app, and sales channel still control the final requirement.
Open Shopify's current Product Media guidancehttps://help.shopify.com/en/manual/products/product-media/product-media-types
Google Merchant Center
Main product image guidanceLast reviewed: August 20, 2026
Google has announced a minimum of 500 x 500 pixels for all products beginning January 31, 2027 and recommends 1500 x 1500 pixels or above. Its current guidance limits images to 64 megapixels and 16 MB, recommends product fill between 75 and 90 percent, and restricts promotional overlays, borders, placeholders, and mismatched variants.
Google separates minimum requirements from best practices and can update enforcement dates. Verify the current Merchant Center source and the account's Diagnostics before delivery.
Open Google Merchant Center image guidancehttps://support.google.com/merchants/answer/6324350
These links are references, not endorsements. Lenso does not monitor them continuously or guarantee that a file will be accepted by the destination.
When the record needs to stay with the job
Lenso keeps the requirement and client decision attached to the work.
You can use this framework with any toolset. In Lenso, the studio can keep the current brief, SKU and shot rows, proof versions, comments, requested changes, approval history, optional invoice, delivery manifest, and final files connected to the same job.
- Structured brief and shot requirements
- SKU and shot-list context
- Proof uploads and versions
- Asset comments and requested changes
- Recorded approval history
- Optional invoice and payment context
- Protected previews and final-file release
- Delivery ZIPs and CSV or XLSX manifests
- Project-specific secure client access
- Client-facing delivery filenames
- The studio reviews every request before it becomes a job.
- Client access is project-specific and Lenso-hosted.
- Secure links can expire or be revoked.
- Clients do not need a paid seat.
- Source storage names can remain different from client-facing delivery filenames.
What Lenso does not check automatically
Lenso records the job context and decisions. It does not currently certify the visual or technical quality of an image.
- Whether the product color matches a physical sample
- Whether a crop is creatively successful
- Whether retouching is truthful
- Whether a label or package claim is legally accurate
- Whether an image meets every Amazon, Shopify, Google, retailer, or marketplace rule
- Whether a display is calibrated
- Whether the physical product arrived in acceptable condition
- Whether the client agreement makes an approval legally binding
- Whether a file will be accepted by a third-party destination
- Whether a final image should pass the studio's creative standard
A qualified person still reviews the work and applies the current client and channel requirements.
About this quality-control framework
- Is this an industry certification?
- No. It is a practical checklist created by Lenso for product photography studios. It does not certify a studio, file, person, process, or destination.
- Is a pure white background always required?
- No. Some main-image destinations require white, while other jobs use transparent, colored, environmental, or lifestyle backgrounds. Use the current approved requirement for the file.
- Should every product fill 85 percent of the frame?
- No. The 85-percent figure belongs to Amazon's current US main-image guidance, not every product image. Secondary images, other channels, and client-owned stores can use different framing.
- Is sRGB always the correct color profile?
- No. sRGB is common for web delivery, but the current client or destination specification controls. Record the required profile and verify the actual export.
- Does a checked item prove legal acceptance?
- No. The checklist is an operational record. The client agreement and applicable law define the effect of approval, silence, delivery, and acceptance.
- Can automated tools replace a human review?
- Not for the full decision. Automation can assist with narrow technical checks, but product truth, color, styling, retouching, exceptions, and client acceptance still require the appropriate person.
- Does Lenso inspect images against marketplace rules?
- No. Lenso keeps the brief, shot context, proofs, requested changes, approval, and final files connected. It does not currently validate an image against every marketplace or retailer rule.
- Who should make the final decision?
- Record the person authorized to approve the current files for the client. The person who sent the original request may not be the final decision maker.
- How should the studio handle an accepted exception?
- Name the affected SKU or file, describe the deviation, record who accepted it and when, and keep the decision with the final job record.
- Can I use this without Lenso?
- Yes. Print it, adapt it to a spreadsheet or studio process, and use the system of record that fits the job.
Build the source record
Give the reviewer a clear requirement to check.
Quality control is easier when the brief, product rows, and delivery handoff are already explicit.
Product photography shot list template
Record one row for each SKU, variant, and required view, including styling, reference, output, and delivery-name details.
Product photography production checklist
Record the owner, evidence, and completion condition for request and scope, production, review, final-file QA, and delivery.
Security and file access
Read how Lenso handles account access, secure client links, private files, Stripe payments, export, and current security limits.
From quality check to final release
Keep the proof, decision, and final file in the same job.
This checklist works with any toolset. Lenso is useful when a studio wants the current brief and shot rows, proof versions, client comments, requested changes, approval, optional invoice, and final files to remain connected.
Lenso does not decide whether an image is good enough. The studio and client use the current requirement and record the decision.