Start with the recipient and how the images will be used
- Tie fit and construction approval to the exact garment version.
- Use CLO for a fixed garment still when its in-app render meets the brief.
- Give the render partner the approved garment, fabric and color references, target views, and recipient-specific image specs.
- Treat approval of the finished image as a separate presentation decision.
Approving a garment and approving an image of it are two different decisions. CLO offers a straightforward in-app route when the team needs a still of its simulated garment: its rendering guidance describes rendering as simulating real-life lighting and reflection on the 3D garment. When working with an external partner, the goal is to keep the approved garment and material state clear while spelling out what remains open: the view, destination, and visual treatment.
1. Separate garment approval from image approval
Begin with a clear record of what the product team approved. Note the garment-file version, base size and grade, avatar or body measurements used, fabric assignment, colorway, and technical review date. That gives the image partner a dependable reference instead of the vague direction to render “the approved sample.”
Fit approval and image approval serve different purposes. Fit review documents whether the garment’s shape, construction, and material behavior meet the team’s technical standards. Image review asks whether a particular view communicates the product well for a line sheet, product page, or buyer presentation. A fit model can also describe how a garment feels or moves on the body—information a still image cannot convey.
A 2024 study in Fashion and Textiles describes fit teams using visual cues such as unintended wrinkles to identify issues and adjust the 2D pattern. It also reports that fit models’ comments about garments digging in or feeling snug can provide useful feedback. Keep those technical notes with the approved sample. Send presentation notes—such as crop, lighting, pose, and framing—as a separate list for the render partner.
For a garment developed in CLO, keep the simulated garment state with its review record. In a study of men’s T-shirt development in a CLO virtual environment, the authors used strain mapping to review tension distribution and fitting conditions. They reported that simulation accuracy depended on proper fabric-parameter calibration and user expertise. The practical takeaway is simple: include the approved fabric setup or its matching material reference, rather than expecting a renderer to infer fabric behavior from a flat image.
CLO-SET can help keep that approval trail together. Its brand workspace supports comments, annotations, and version tracking directly on 3D designs, giving teams and external partners a shared place to refer back to the garment and its feedback.
2. Specify the images before choosing the render route
Turn the recipient’s needs into a shot list before anyone opens the file. A product page might need front and back views, an angle that shows the silhouette, and close-ups of features such as a pocket, closure, or texture. A line sheet may call for consistent front views across styles, while a buyer presentation may need a broader selection of colorways.
For e-commerce, an on-avatar view can help communicate length, proportion, and how the garment sits. Baymard’s apparel usability research describes shoppers using model imagery to assess garment features. Its apparel sizing research also observed shoppers using model measurements alongside a size guide. Together, these findings point to a useful product-page approach: show the garment on a representative avatar and provide fit or size information separately.
Set out the pixel dimensions, aspect ratio, file type, background, crop-safe area, naming convention, and image count by colorway and size. Including these details up front helps avoid a familiar snag: a polished master image that still needs a new crop or export to work on its intended destination.
Platform guidance shows why the image brief should be specific to its destination. SHOPLINE’s OS Theme 2.1 guide offers square (1:1), portrait (2:3), landscape (4:3), and original product-image scales, and advises choosing a scale that suits the product’s shape. Shopify’s image-size guide recommends square product thumbnails at 150–300 pixels and notes that square or vertical images work well on mobile screens.
Comparison table Scroll to view every column ↔
| Deliverable | Brief it for | What the view helps the recipient judge |
|---|---|---|
| Main product image | Front or three-quarter view, specified crop and background | Overall silhouette and product identity |
| Construction detail | Close view of a named feature, such as a seam, closure, or trim | Visible design details |
| Colorway set | Same framing and lighting for every approved colorway | Differences among the requested options |
| Size-range set | Identified grade sizes and consistent camera framing | How the graded versions look side by side |
| Buyer or line-sheet view | The recipient’s requested angle, background, and dimensions | The garment in the intended review context |
3. Use CLO for a defined still, and match the workflow to the deliverable
Choose the render route based on the image the team needs, not a general idea of which software is “best.” For a fixed still of a simulated CLO garment, CLO’s documented render process adds lighting and reflection to the 3D garment within the product workflow. It is a strong first option when the approved pattern, material, and colorway are already in the garment file and the resulting image meets the destination brief.
Comparison table Scroll to view every column ↔
| Route | Choose it when | Handoff implication |
|---|---|---|
| Render in CLO | The deliverable is a fixed image of the approved simulated garment, and the in-app view meets the brief | Keep the garment, material setup, selected view, and approved version together |
| Use CLO-SET to support review and coordination | The team wants comments, annotations, and versions connected to the 3D design | Keep feedback attached to the relevant design and make the approved version clear to everyone involved |
| Work with an external image-finishing partner | The brief calls for added scene-building, compositing, or motion beyond a fixed garment still | Agree on accepted input files, retained garment details, output format, and a test render before transferring a full collection |
When reviewing graded sizes, CLO’s Grading Review guide describes simulating and reviewing sizes, then comparing them in a single 3D window. Use that technical review to support the size decision, and use the image set to communicate it.
Label each rendered view with the size and colorway it depicts, and link the delivery folder or approval record to the exact garment version reviewed. Images can show how graded sizes look; the technical sign-off should still document the fit review behind those sizes. In CLO-SET, version tracking and feedback on the 3D design can help keep that record and the related discussion together.
4. Prepare a render-partner handoff that protects the approved state
Give the partner a concise brief with four parts: the approved source, the visual target, the technical references, and the review process. Ask which garment file or export their workflow accepts and what information remains editable after transfer.
A practical handoff pack contains:
- The approved garment version and the base size or graded sizes requested.
- The matching fabric or material reference, colorway names, and approved color standard.
- The required front, back, angle, and detail views, with camera and crop notes.
- The recipient’s dimensions, aspect ratio, background, file format, and delivery naming rules.
- One reference image or annotated screenshot showing the intended lighting, framing, and detail emphasis.
- A review contact, a revision limit or schedule agreed with the partner, and a named approver for the final images.
CLO-SET can also provide a shared place to review the 3D design and keep comments and version history connected to it. If the team uses it for the handoff, confirm that the partner has access to the right version and that the final image files will be stored or linked where reviewers can find them. The render brief itself should still state which garment details, materials, and views must be preserved.
Color needs a clear reference, too. X-Rite’s Textile Color Hub documentation describes color specifications that can include spectral data, supplier matching tolerances, and illuminants—the lighting conditions used for measurement. Include the brand’s approved textile color reference when material color matters, and separately agree on the intended appearance in the still. An embedded ICC profile helps software translate image colors between devices; textile color data gives suppliers a physical color target.
5. Review one representative image before the full set
Ask the partner for a test render of one representative garment, colorway, and view before commissioning the full set. Compare it with the approved source and written brief. Check the silhouette, seams, trims, fabric texture, colorway, avatar pose, camera framing, and background. If something is off, identify whether the issue is in the garment state or the image treatment so the correction reaches the right person.
Review the image in its intended destination, especially if it will appear on mobile. In its OS Theme 2.1 guide, SHOPLINE explains that components such as “Large image with text box” and “Slideshow” may crop images when fixed heights do not match their dimensions. In these components, responsive processing zooms and crops wide images to cover the display area on desktop and mobile.
Once the test is approved, agree on the image rules that should stay consistent across the set: camera angle, crop, background, lighting, and file naming. Ask for a contact sheet or review sheet that identifies each image by style, size, colorway, and view. A clear review sheet makes it easier for product and merchandising teams to catch a missing option before the files reach a buyer or storefront. If feedback is managed in CLO-SET, its comments and annotations can remain attached to the 3D design rather than getting separated from the item under review.
6. Release a final still-image pack with two clear approvals
For Shopify product images, Shopify’s image-size guidance allows uploads up to 5,000 × 5,000 pixels and 20 MB. The same guide recommends 2,048 × 2,048 pixels for square product images—a platform-specific target when the recipient requests square artwork. For other storefronts and buyer portals, confirm their current image dimensions and upload limits before exporting.
A complete image delivery includes the approved image files at the recipient’s requested sizes, consistent file names for style and size, colorway labels, the source-version identifier, and the image-approval record. Keep garment approval and image approval distinct: CLO provides a capable in-app route for a fixed garment still, while CLO-SET can help teams keep the 3D design, version history, and review feedback organized. Bring in an external image-finishing partner when the brief calls for scene-building or motion beyond the still.