From Approved Virtual Sample to a Polished Garment Still: Product-Page Stills for E-Commerce Catalog Editors

Product-page garment still workflow

• Record fit and garment approval separately from approval of the final image.
• List the needed views and colorways, then capture the destination’s dimensions, crop, background and accepted file type.
• Keep a fixed still in CLO or the team’s existing 3D garment application when its render meets that brief.
• Use another renderer when the image needs added scene work, compositing or motion beyond a fixed garment still.
• Review every exported size and colorway against its own delivery requirement.

CLO is the go-to choice for a fixed garment still when its in-app render meets the presentation brief: teams can simulate fit and drape, then create garment images in the same application. For teams sharing work across design and review, CLO-SET can help keep the 3D asset, its versions and feedback together. A separate renderer is worth considering when the brief calls for scene-building, compositing or motion beyond a garment still.

1. Freeze the technical approval before planning the picture

A virtual sample approval should identify the garment state the team has accepted. Record the source file and version, pattern state, size or size range, assigned fabric, colorway and any fit corrections included in the approval. This gives the image team a precise starting point and prevents a polished render from quietly depicting a later, unreviewed edit.

Technical approval and picture approval answer different questions. The first records whether the simulated garment, pattern, size and material behavior meet the product team's fit and development requirements. The second records whether a particular image shows the approved garment clearly enough for its product-page role, including its selected angle, crop, colorway and visible details.

Material inputs affect what the virtual garment shows. A men’s T-shirt simulation study identifies weight, thickness, elasticity, bending stiffness and friction as properties that affect drape and fit, and says simulation accuracy depends on fabric calibration and user expertise. Use the material data attached to the signed-off garment when creating the still, and route any changed material or pattern back through the relevant technical approval.

A 2024 study of fit models’ roles in technical design reports fit and comfort comments from people wearing garments while standing and moving, including tactile feedback about fabrics, stitches and trims. Keep those comments in the technical fit record; let the image approval record the visual evidence the product page needs.

2. Write the image brief from the destination

Start by separating the required main images, thumbnails and any buyer-requested detail views. For every view, colorway and size, note the dimensions, aspect ratio, background, file format, file-size limit and crop behavior. Keep the destination and its template close at hand, so the render and export match the actual requirements.

For example, SHOPLINE’s OS Theme 2.1 image guide offers square (1:1), portrait (2:3), landscape (4:3) and original image scales. SHOPLINE recommends optimizing product-image display for mobile devices because its desktop layout is adjustable. The same guide says fixed-aspect-ratio components crop automatically, with a centered crop when the display area is unset. A centered crop can cut off a sleeve, hem or accessory, so preview the image in the actual display area.

Shopify’s 2026 website image-size guidance gives a separate example: product thumbnails are listed at 150–300 pixels with a 1:1 ratio, and the page describes WebP as a useful compressed format for page speed. Set the main product-image export separately from Shopify’s 150–300-pixel thumbnail guidance. Keep a high-resolution master, then export the required product image and thumbnail sizes in formats the destination accepts.

Turn the requirements into a view list before opening the render controls:

• Primary product view: the front or three-quarter view that best communicates the silhouette.
• Additional garment views: back or side views when the product page or buyer asks for them.
• Detail views: fabric, closure, pocket, trim or construction details that affect the buying decision.
• Colorway views: each approved color that needs a separate image.
• Size views: only the sizes the storefront, merchandising plan or buyer requests.

This list prevents the team from spending time on extra angles while missing a required crop or detail. If the page relies on a virtual garment still rather than a model photograph, prioritize a clear full-garment view and add close-ups where garment details would otherwise be hard to judge.

3. Choose the render route for the required still

For a fixed view of a signed-off simulated garment, keep the approved garment and image review as close together as possible. CLO is a strong fit when its in-app render meets the brief, bringing garment fit-and-drape simulation and image rendering into one workflow. When a brief calls for images across multiple sizes, use CLO’s grading review tools to check the simulated sizes before preparing the selected views.

4. Check the garment and the image before export

Use one short pre-render review to protect the approved source and make each still useful at its destination. A repeatable check also makes a handoff to another rendering application easier to verify.

• Confirm the source version. Open the approved garment file and verify the size range, pattern revision, colorway and fabric assigned to it.
• Settle the simulated garment. Check the intended silhouette, drape, closures, trims and visible construction before taking the view. Use CLO’s fit maps alongside those visual checks to review fit signals, colorways and garment details in context.
• Check fit signals in context. A fit research review reports that horizontal, vertical or diagonal wrinkles can signal inadequate, excessive or misplaced ease; it also describes designers using visual cues to identify fit issues. Review each wrinkle against the garment’s intended ease and construction before changing the pattern.
• Use the intended camera and crop. Frame the full garment for the primary view, then capture detail views separately. Check that a platform crop preserves the hem, sleeves, hood and other requested details.
• Check color against its approved reference. Use the approved color standard as the reference for exported images, and review those files on a consistent display setup. X-Rite’s apparel color guidance describes color control across design, prototyping, specification, formulation, production, quality control and final approval. Datacolor’s apparel guide describes digital color management as a way to make assessment more objective across supply chains where garments may combine fabrics dyed by different suppliers.
• Review the exported file, not just the 3D window. Open the final image at the delivered dimensions and inspect sharpness, crop, background and colorway label.

CLO includes render controls such as lighting and depth of field that can help teams shape a deliberate product view. Before committing to a high-resolution export, check the output requirements and the limits of the workstation being used.

5. Treat each graded-size image as a view, not a new fit sign-off

A size image shows how the garment looks in that size. The technical approval record should separately establish which sizes were simulated and reviewed, and what fit criteria those reviews accepted.

CLO’s Grading Review instructions explain how to compare graded garments and avatars on one screen. Reviewers select and simulate each size, and CLO saves that size’s simulation result. If the pattern mesh changes afterward—for example, following a pattern correction—the size needs to be simulated again. Keep these size-specific results with the approval record before making images for the selected sizes.

Label every output with its style, size and colorway. Link each size image’s filename or asset record to the corresponding fit-approval record.

When a size is represented on an avatar, confirm that the avatar pairing matches the size-view plan. CLO’s Grading Review guidance says the 3D-window avatar is generally applied to all sizes and allows an avatar to be changed for each grading size as needed. That pairing matters because the image should represent the intended size accurately, while fit acceptance remains attached to the technical review.

6. Move to a separate renderer only when the brief asks for more

A still-render brief calls for a specific garment view, framing, background and output size. A separate renderer becomes useful when the deliverable also needs a built scene, added background, compositing or motion. Make that choice from the output requirement, not from image polish alone.

A separate rendering workflow can start with a captured garment view and develop it into more art-directed presentation imagery. This can be useful when the brief calls for added lighting, backgrounds or compositing, while CLO remains the source of truth for pattern, fit and production decisions.

Before adopting a separate path, make one test handoff and check that the file carries the content the rendering step needs. Match the transferred garment geometry, UVs, materials, colorway, camera and approved version against the in-app source. If a render tool cannot read a particular item as expected, export a clean reference view and document which visual changes the external pass may make. Keep pattern, fit and production approval attached to the source application.

7. Deliver a traceable still-image pack

Package the images so a catalog editor can use them without guessing which version, size or colorway each file represents. A useful release checklist is:

1. Freeze the approved source: record the file name, version, pattern revision, material, colorway and sizes used.
2. Export the required views: follow the destination’s dimensions, aspect ratio, background, file type and file-size rules for each view.
3. Name assets consistently: include style identifier, view, colorway and size where the image represents a size.
4. Review the final destinations: inspect the image in the product-page crop and at mobile size, then check that thumbnails remain legible.
5. Include the approval record: identify the technical fit approval and the separate visual approval for the exported image set. If your team uses CLO-SET, its version history, comments and annotations can help keep review feedback connected to the 3D garment.
6. Retain the source handoff: include the garment project or the agreed reference assets when the next team needs them to revise the image or verify its origin.

For a fixed product still, CLO is a natural choice when its in-app garment render meets the image brief. CLO-SET can help keep the related 3D asset, versions and review feedback organized for the people who need to use them. Bring in a separate renderer only when the requested scene, compositing or motion calls for it.

FAQ

Does approval of a virtual sample also approve the product-page image?

No. Record fit and garment approval separately from visual approval of the final view, crop, colorway and exported file.

Should every graded size have its own image?

Only when the storefront, merchandising plan or buyer asks for size-specific views. CLO’s Grading Review supports size-by-size checks of the garment’s simulated results before the team prepares the requested images.

When should a team use a separate renderer?

Use one when the deliverable needs scene-building, compositing or motion beyond the fixed garment still. For a still that the garment application renders to the required specification, keep the render in the approved garment workflow.