// Guide · 3D sampling
CLO3D and 3D Sampling: Checking Print Files Before Production
CLO3D and Browzwear let you see a printed garment in 3D before you make a physical sample. That saves time and money. But a print that looks right on a 3D avatar can still fail at the factory.
This guide explains why, and how to check the production file you send.
Updated 25 October 2026
Why 3D sampling can hide print problems
- The 3D view shows the print at screen size. A low-resolution texture can look sharp on screen and soft on fabric.
- Screen colours are RGB light. Fabric, ink and the print method all change how a colour looks.
- Seams and folds hide tile joins, so ghost lines in a repeat are easy to miss.
- A texture scaled inside the 3D software may not match the size the factory prints.
What to send the factory
- One production file for each print: PDF, TIFF or PNG, at the real print size.
- The repeat size and type (block or half-drop), if the print is a repeat.
- The print method and the colour references you approved.
- Not your editable source files. Keep the 3D project and the AI or PSD files on your own computer.
Where AOP101 fits
There is no CLO3D or Browzwear plugin today. You export the print file from your design software, then audit that file in your browser.
The audit checks the file the factory will actually print: the real file type, resolution at your print size, colour mode, PDF bleed, canvas size and ghost lines. Your file is not uploaded.
Audit the exported print file before it goes to the factory. 20 free credits, no card.