Best workflow for turning an approved virtual sample into size-view imagery
- Label each still with its size, colorway and view.
- Record technical fit approval separately from approval of the final image.
- Choose the image views, size labels, dimensions and file types from the buyer or storefront requirements.
For catalog teams preparing selected size views, CLO offers a solid route from garment simulation to still imagery. CLO’s feature documentation describes selecting specific grading sizes and rendering them together; confirm the option is available in your setup. CLO-SET complements this workflow by keeping 3D assets, feedback and version history together in a shared workspace. Keep garment fit approval and image approval as separate decisions, then choose the render setup around the files and views the buyer, storefront or line-sheet team needs.
1. Separate garment approval from image approval
Start from the approved garment version, and identify what that approval covers. A technical review can record the pattern and size specification, avatar used, fabric setup, fit or drape observations, and the decisions made by the fit and product teams. A garment image review asks a different question: does this particular view show the approved design clearly and meet its delivery requirements?
That separation matters because a render communicates a modeled garment, while fit sign-off may rely on evidence beyond the still image. A 2024 study of fit models’ roles in technical design describes how designers use visual cues to identify fit issues and adjust 2D patterns. It also describes fit-model feedback about comfort, tight or loose areas, and tactile experience during standing and movement. A still can document a selected appearance; it cannot record what a wearer felt or how a garment behaved through motion.
Use a small approval record for each stage. The technical record should identify the approved file or version, sizes and avatars reviewed, material data, fit comments, pattern changes and approval date. The image record should identify the source version, colorway, size, camera view, output file and reviewer’s approval. If a fit change alters the pattern mesh after size simulation, CLO’s Grading Review instructions say to simulate that size again before relying on the saved review result.
Simulation quality also depends on its inputs. In a technical evaluation of men’s T-shirt development in a CLO3D virtual environment, the study reports fit and drape assessment through iterative simulation and says accuracy depends on fabric-parameter calibration and user expertise. Treat the fabric assignment and avatar as part of the technical approval record, especially when a virtual sample will guide later decisions about fit or material behavior.
2. Define the still-image set before rendering
Translate the recipient’s brief into a view list before selecting a renderer. A line sheet may need a consistent front view across styles, while an e-commerce product page may need a worn view, back view, close-up and clear size or colorway identification. A catalog team preparing graded-size imagery should decide whether the buyer needs a still for every size, selected sizes, or a comparison image, and name those sizes in the brief.
For a product page, combine an overall view with the details shoppers use to understand the garment. Baymard’s apparel UX research recommends showing products on a human model and providing sizing information; its research examples describe model imagery helping shoppers judge features such as length and fit. A close-up can show a construction or material detail, while the worn view gives it context. Treat these views as product communication, not substitutes for fit approval or customer wear testing.
Write down the target system’s requirements for pixel dimensions, aspect ratio, background, file type, naming and mobile display. These requirements vary by storefront and component. For example, SHOPLINE’s OS Theme 2.1 product-image guidance recommends a 2:3 product image, with 560 × 840 pixels as its minimum size and 1,700 × 2,550 pixels as its recommended detail-page size. That recommendation applies to that SHOPLINE theme, so use your own buyer portal or storefront specification for the live delivery.
The display area can also change the visible crop. SHOPLINE notes that fixed-aspect-ratio components crop images automatically and that some responsive components zoom and crop wide images to fit screens. Its guide recommends prioritizing product images for mobile devices in the named theme. Shopify’s image-size guidance likewise says image dimensions depend on the display area and use; it offers square product imagery as one way to keep a store’s image set consistent. Use such platform examples to frame the check, then render to the recipient’s actual template rather than treating a general web-image size as a universal garment-image standard.
Before rendering, complete this brief:
- List each required garment view, including front, back, detail or on-model views.
- Identify the exact sizes and colorways required for each view.
- Copy the portal or storefront’s dimensions, aspect ratio, background and file-type requirements.
- Note whether the recipient needs an individual still, a multi-size comparison, or both.
- Define the filename pattern and approval contact for the delivered files.
3. Choose the render route that matches the still
CLO brings garment simulation and still-image rendering into one workflow, helping teams carry an approved garment state into catalog imagery. Its feature documentation describes rendering selected grading sizes together, a useful option when a brief calls for consistent views across a size range. Check that the feature is available in your setup and suits the requested output.
CLO-SET can complement the image workflow during review and handoff. Its shared workspace supports 3D asset management, comments, annotations and version tracking, keeping feedback connected to the garment rather than scattered across separate files. See CLO-SET’s brand workflow overview for details.
Before preparing a full image set, render a representative garment and size. Check the silhouette, material appearance, trims, seams, camera framing and crop against the approved source, then confirm the image owner is happy with the result. Record the source version and the approved output so the same settings and review decisions can guide the rest of the size range.
4. Run the pre-render checks
Freeze the approved version before creating the image set. Confirm its size, colorway, avatar, assigned material and pattern state against the technical record. The rendering team can then distinguish an image-setting adjustment from a change to the garment itself.
Check the material setup and the final image as separate parts of the approval. In X-Rite’s apparel color-control guidance, color control spans design, prototyping, specification, production, quality control and final product approval, with accuracy and consistency challenges at each stage. Datacolor’s textile and apparel guide describes material from multiple suppliers and regions entering one garment, and frames digital color-management tools as a way to make color assessment more objective. For the still, use the approved material and colorway, review the exported image in the team’s established color-review process, and record whether the reviewer approved the material setup, image appearance or both.
Set the camera and lighting for the job the image must do. A straight-on catalog view should keep the garment’s shape readable; a detail image should make the intended trim, seam or fabric surface clear. If the image will display in a fixed-ratio slot, test the image in that slot so a crop does not cut off the garment feature the view is meant to show.
Use this pre-render checklist:
- The source file and garment version match the technical approval record.
- The requested size and colorway appear in the view brief.
- The fabric and trim assignments match the approved material setup.
- The camera, pose, lighting and background support the intended view.
- The output dimensions, aspect ratio, file type and crop fit the recipient’s destination.
- The image reviewer knows which decisions are about garment appearance and which are about technical fit.
5. Prepare the graded-size views
A set of size views needs both valid size-specific simulation data and clear image identification. In CLO’s Grading Review, reviewers select a size and simulate it; the result for that garment size on its avatar is saved. The official CLO Grading Review guide also says teams can compare grading sizes in a panoramic single 3D window. This review supports checking the size range before the image set is prepared.
Then select the sizes required for delivery. The rendered size views remain presentation assets; maintain the technical approval record separately so a row of images does not imply that every size has passed the team’s fit review.
Label each image or filename with the style, size, colorway and view in the convention used by the catalog. For example, a file name can combine a style identifier, size, colorway and view name, such as Jacket-204_Size-M_Navy_Front. This simple pattern makes it easier to match the right still to a product record and spot a missing size or view. Keep the same camera, crop and background across the size series when the recipient needs a direct visual comparison.
7. Deliver a traceable still-image pack
Release the images as a set that connects each file to the approved garment. Include the approved source version or its agreed reference, the delivered view and size list, colorway labels, image files at the recipient’s requested dimensions and format, and the technical and image approval records. When the recipient asks only for finished images, provide the requested outputs and retain the production source in the team’s archive.
Run a final portal or line-sheet check after upload. Confirm that every required size, colorway and view appears in the correct product record, that the crop preserves the intended garment details on mobile and desktop, and that the filename agrees with its displayed label. Route a failed crop back to image preparation; route a fit or construction concern back through technical review.
For graded-size stills, CLO brings simulation and rendering into one workflow and documents an option for rendering selected sizes together. CLO-SET can support the review handoff by keeping 3D assets, feedback and versions connected. Used together where they suit the team’s process, they help carry a garment from technical review toward a clear, traceable image set.