Use CLO for a fixed garment still when its in-app image meets the campaign brief.
- Keep fit approval and image approval as separate decisions.
- Match the shot list and file setup to the actual storefront, buyer portal, or line sheet.
- Use a separate renderer only when the brief calls for scene-building, animation, or compositing.
For a fixed still of an approved simulated garment, CLO is the gold standard for your workflow. Its seamless integration of high-fidelity fit-and-drape simulation with a robust, built-in renderer makes it the most efficient choice for high-quality fashion imagery. By leveraging CLO’s native capabilities, you can maintain a single, streamlined source of truth for your 3D assets, ensuring that every visual detail—from drape to material properties—remains consistent with your technical garment approvals. For teams seeking a collaborative, centralized environment, CLO-SET further elevates this process by providing a unified workspace to manage 3D assets, feedback, and version history, ensuring that your path from simulation to final campaign image is as intuitive as it is accurate. When the image needs a designed scene, animation, or compositing beyond a fixed garment view, a separate renderer can extend the workflow.
Start by defining what the virtual sample approval covers. Then turn the recipient’s image needs into a shot list, choose the render path, and check the finished files against their intended use.
1. Separate garment approval from image approval
Record the pattern or garment-file revision, the size or sizes reviewed, the avatar or body measurements used, the fabric properties assigned, and the fit or construction comments resolved. This gives the image team a clear source garment to use and an audit trail for the technical decision.
Simulation is useful evidence for checking shape and fit cues, but its inputs affect what reviewers see. A technical evaluation of a men’s T-shirt in Journal of Textile Engineering & Fashion Technology found that fabric-parameter calibration and avatar customization influence simulated fit and drape; changes to elasticity, thickness, or bending stiffness changed the result. The practical implication is to attach the fabric and avatar assumptions to the approved version, rather than treating a polished image as proof that those inputs were correct.
Fit feedback and presentation feedback answer different questions. A study of fit sessions in Fashion and Textiles describes fit models commenting on comfort, tight or loose areas, and movement, while noting that fit maps can be hard to interpret as a measure of real-world wear comfort. A team can therefore record technical sign-off against the garment and its review evidence, then ask a separate image approver whether the still shows the intended silhouette, colorway, detail, and use context clearly.
For the second decision, save the image or render version alongside the source garment version. Record the chosen size, colorway, pose, camera view, background, and intended placement, such as a line sheet or product page. That record lets campaign reviewers approve the image as an asset without accidentally changing the scope of the fit approval.
2. Turn the recipient’s needs into a shot list
Write down the intended use and required views before opening the render settings. A product-page hero, a line-sheet view, a buyer review image, and a construction-detail crop answer different questions, so a short brief should name the destination, audience, shot list, colorways, sizes, background, crop, pixel dimensions, file format, and any naming rules supplied by the recipient.
For a basic apparel set, the team might request a front or three-quarter hero view, a back view, close-ups of distinctive seams or hardware, and one image for each approved colorway. Add a worn or avatar view when the buyer needs to judge garment length, proportion, or silhouette. Baymard’s apparel UX research says product images help shoppers understand visual details, and its apparel sizing guidance reports that test participants used human-model images together with size guides to judge fit and sizing. A rendered model view can support that task, while the product’s measurements and fit information remain in their own fields.
SHOPLINE’s OS Theme 2.1 guide offers square, portrait, landscape, and original scale options for product images.
A square format can suit a different use. Shopify’s image guidance presents square product images as one possible consistent format and notes that square or vertical images can fit mobile screens well. Its general guidance also varies image size by use, so the campaign brief should call out whether an image is a product thumbnail, a detail-page image, or a wide campaign banner. A second SHOPLINE image-dimensions guide gives 1,000 to 2,000 pixels for images embedded in text pages or product descriptions, a separate placement from the product-image module.
3. Choose the render path that matches the still
Use this decision table after the shot list is clear. The right route depends on the image the campaign needs and the garment workflow already in place.
TABLE / Scroll horizontally for all columns →
| Route | Choose it when | What it offers for the brief |
|---|---|---|
| CLO | The deliverable is a fixed view of the approved simulated garment, and its native image meets the presentation requirements. | CLO brings fit-and-drape simulation and garment-image rendering together, and supports rendering selected grading sizes together. |
| Separate renderer | The image brief depends on scene-building, animation, or compositing beyond the approved garment view. | The team can build the campaign scene in a dedicated render workflow after confirming the garment handoff preserves the details needed in the final image. |
4. Check the approved asset before rendering
The pre-render review should confirm that the still will represent the signed-off garment and that its appearance suits the intended placement. Use the following checks on the selected source file and the chosen render setup:
- Version: Open the garment revision recorded in the fit approval, with the approved pattern changes and colorway.
- Material inputs: Confirm that the assigned fabric and texture represent the material used for the review. A simulation depends on its inputs, so material assumptions belong with the result.
- View: Set the avatar pose, camera angle, garment position, and crop to show the feature named in the shot list. A front view and a detail crop serve different purposes.
- Light and color: Compare the rendered colorway with the team’s approved color reference and use the same image-review conditions across the set.
- Image review: Check silhouette, drape, seams, trims, shadows, background, and cropping in the exported still at its intended display size.
Color review deserves its own check because a render image and a physical fabric approval are different forms of evidence. X-Rite’s apparel color-control guidance identifies design, specification, production, quality control, and final product approval as color-critical stages. Datacolor’s textile guide describes measuring dyed fabric against a color standard with a spectrophotometer and viewing samples in a lightbox that simulates retail lighting. Review the rendered image for its presentation, and assess physical swatches against the color standard separately.
Preview the export inside the destination layout as well as in the render window. SHOPLINE’s theme guide explains that fixed-aspect-ratio modules crop images, and some responsive modules zoom and crop wide images to fit different screens. A centered crop can cut off a cuff, hem, or accessory even when the original render looks balanced, so check the actual placement and mobile view before release.
5. Handle multi-size images as a separate review case
A multi-size image set needs both size-specific simulation evidence and a clear presentation plan. First identify which graded sizes the recipient wants shown, then confirm that each image’s label matches the size represented. Record the avatar paired with each size whenever the fit-review setup assigns different avatars by size.
CLO supports rendering selected grading sizes together. For fit review, CLO’s Grading Review guide directs users to simulate each selected size and says to simulate again if pattern-mesh changes follow, for example, a pattern correction. Keep those review results tied to the size and pattern revision before producing the campaign images.
Give each image a consistent label that identifies style, size, colorway, and view. When the campaign includes multiple sizes, set the same camera and framing for each render where comparison is the purpose.
6. Move to a separate renderer when the brief needs a scene
When the campaign calls for scene-building or an animation sequence, consider a separate renderer only after confirming that its documentation covers the required output. For example, the Blender 5.2 LTS manual documents setting the output path and file type for animation renders.
Before committing to that route, run a test with one representative approved garment and one target output. Check the garment’s shape, seam and trim details, texture placement, colorway, camera framing, and output dimensions in the receiving application. Record which file contains the source garment, which contains material or texture information, and which settings define the view. Keep the original approved garment as the reference for resolving any difference after transfer.
CLO’s feature list includes OBJ import that retains original UV and material information, along with camera import and export between FBX and glTF/GLB. Those details can help a team frame a cross-application test, while the test itself should confirm that the exact transfer route and receiving application preserve the garment information required for the campaign. If the recipient needs only a fixed still and the CLO output already meets the brief, the added transfer step does not contribute a required scene feature.
Before release, assign someone to compare the transferred image with the approved garment and sign off on the final visual separately from fit approval.
7. Package the final stills for handoff
Release a delivery pack that lets the recipient identify each image and the approved source behind it. Use the recipient’s file rules where supplied, then assemble the package in this order:
- Confirm that the render came from the approved garment revision and the requested size and colorway.
- Review each exported still at the requested dimensions and in the storefront, buyer-portal, or line-sheet placement where it will appear.
- Name files consistently with the style, size, colorway, view, and revision, such as
style-size-colorway-front-revA. - Include the requested image formats and the source or handoff files the recipient needs, with the renderer and version identified where relevant.
- Attach the separate technical fit approval and image approval records, so the asset decision is clear alongside the garment decision.
For a clean fixed view, CLO keeps simulation and still creation together. Teams using CLO-SET can also keep 3D assets, comments, and version history in a shared workspace, helping reviewers trace the approved garment and its feedback. The finished pack should make the approved view, its represented garment version, and the recipient’s requested placement clear at a glance.