CLO Plugin Downloads
v2.0.5
Version 2.0 sees a complete rework of the plug-in with added functionality in the form of download and import. This version also sees support for CLO version 2025 and newer.
CLO 2026.0.262+
CLO 2025.1 & 2025.2
Important Note about 2026.0.238
There is an issue in the API version associated with 2026.0.238 (the initial 2026 release). When the plug-in is built with this version, using it with subsequent 2026 version will fail. Instead, we have opted to build the 2026 compatible version with the API version associated with CLO 2026.0.262 (the second 2026 release). However, in doing so, the plug-in can’t be used with 2026.0.238. Instead, follow this guideline when choosing the plug-in to download for use with 2026:
- Using CLO 2026.0.238 -> Download the plug-in for 2025.1 & 2025.2
- Using CLO 2026.0.262 and newer -> Download the plug-in for 2026.0.262+.
The VNTANA CLO 3D Plug-in simplifies the process of exporting, uploading, and optimizing 3D models—automatically preserving design metadata for seamless collaboration.
With a focus on pattern design and simulated materials, Clo offers a wide range of tools to enhance a users E-commerce space with high quality renders and fabric simulations using their built in simulation environment. VNTANA works to further enhance the Clo users E-commerce space by optimizing the assets designed in Clo, allowing them to be brought directly into your space. With the Clo Plugin, a VNTANA user can export their patterns and garments and have them directly uploaded to the VNTANA Platform for optimization.
Plugin Overview
Plugin Usage
The VNTANA Clo Plugin allows you to easily export your garments from Clo using our recommended export settings and have them directly uploaded to the VNTANA Platform for optimization. The plugin can be used either on an individual garment as a final step in your design workflow, or on a batch of garments.
Installation
Both the MacOS and Windows versions are included in the plug-in package. A set of installation instructions are included in the download. The plug-in does not need to be installed anywhere in particular, you just need to indicate where the plug-in is located to CLO. This is covered within the provided instructions.
Note: The ability to place the plug-in anywhere only applies to plug-in versions from 1.1 on, any prior version must be installed within the CLO installation directory, see that versions included instructions for more information.
Authentication
To make use of the plugin you must first authenticate with the VNTANA Platform using either a valid Authentication Token (see below for instructions on generating this) or email and password. After you’ve logged in once with a valid Authentication Token the plugin will attempt to log you in automatically each time the plugin is launched. There is no option for automatic authentication with an email and password.
Home Page
Upon successful authentication, you will be presented with the home screen, consisting of three areas of importance:
- Menu – located in the upper right corner consisting of your logged in email.
- Platform Settings – located on the left side, this section houses your Organization/Workspace selections as well as search filters when viewing the import screen.
- Workflow Options – located in the center of the window, you can select to utilize the Export or Import Workflows.
Menu
The Menu serves a couple purposes:
- Shows what account you are signed in under.
- Allows you to logout of the current account.
- Provides a quick link to this resources page.
- Enables opening of a Settings window for the plug-in.
Platform Settings
The Platform Settings panel provides selection boxes for the Organization and Workspace you wish to work with on the VNTANA Platform. Selecting these will determine what presets can be used in upload as well as where your uploads will end up during the export workflow, and determines what assets/projects you can access when using the import workflow.
Workflow Options
Export and Optimize
Allows you to select the current garment or a batch of garments to export as a GLB from CLO and upload to the VNTANA Platform.
Import Assets
Allows you to search and download your assets stored on the VNTANA Platform. See below for the list of compatible assets.
Export and Upload Workflow
This workflow allows you to export your .zprj garments as GLB and automatically uploads to the VNTANA Platform for optimization. The export uses our recommended settings from our Export Guidelines, though we do open up a couple of settings. This workflow does have a handful of expectations to work correctly:
- Only processes .zprj files.
- If an Avatar is desired, it must be set and shown.
Upload Options
The first inputs needed for the process are used to determine what should be processed and how they should be organized on the Platform.
CLO File(s)
You can indicate to process the ‘Current Garment Only’, meaning only the .zprj file currently loaded in CLO will be exported/uploaded.
Not selecting ‘Current Garment Only’ means the plug-in will expect to process a batch of .zprj files, which it finds using your input for the Garment Folder path. When processing a ‘Current’ garment, the entered folder path will instead just be used as the destination when exporting the GLB.
VNTANA Platform
This section first allows you to indicate whether to ‘Create Projects’, resulting in all exports being grouped in a Project on the Platform.
Next you can select to upload the source .zprj file, as well as whether it should be uploaded as an attachment on the first colorway or its own Asset on Platform.
You can also indicate if you’d like to export the files DXF. This will upload the DXF as a separate asset with the first colorways pattern layout added as an attachment.
Finally, you can indicate whether to update an existing asset instead of create a new one for each export. Note: this can only search for matches based on file name, so if anything changes in the garment name or colorway names it may not find a match and instead create a new asset.
When updating the Asset, there is also the Version Save Option which indicates how the update should handle versions. The options are:
- New As Current – this will create a new version and automatically set it to new.
- New for Review – this will create a new version for QA.
- Overwrite – this will simply overwrite whatever version is the ‘current’ version.
Note: With the new version options, whatever version is the ‘current’ version will be used as the baseline when creating the new version, replacing relevant settings and metadata based on what was set in the plug-in.
Export Settings
As mentioned above, the GLB export settings are set based on our recommended settings and largely aren’t customizable. This is largely due to the need to prioritize compatibility with our optimization process. There are a couple of options that are exposed though:
- Include Avatar: Will export the Avatar as part of the GLB. This will not work for licensed avatars such as Alvanon avatars.
- Unified UV’s: Indicates whether to export with unified UV’s. This will result in longer export times and higher file sizes.
- Topstitching: Indicate whether you’d like all topstitches to be Texture or OBJ.
- Colorways: Allows you to customize which colorways are exported, except in the case of a batch process. If you are exporting multiple files it will always process all colroways.
Optimization Settings
This page will determine the output of the VNTANA Optimization process. There are three key points here:
- Viewer Preset: This will apply a viewer preset to the optimized assets to ensure your viewer settings are automatically set without needing to manually change them after using the plug-in.
- Optimization Preset: Select from Organization or Workspace level presets to determine your optimization settings without having to manually set them. Selecting a preset will result in the plug-in ignoring the settings in the next part.
- Optimization Settings: Select various settings to determine the geometry and texture optimization levels, apply draco compression, and set a pivot point.
Metadata
The final screen gives you the option of adding Tags and / or Attributes to the products created by the plugin. This is optional and is applied broadly to all products created in that run of the plugin, so if there are any garment specific Tags or Attributes these will have to be created manually on the Platform.
Import Workflow
The Import workflow simply allows you to browse the files you have on the VNTANA Platform and directly download and import them into CLO, with a couple caveats.
Asset Library
As shown above, the Asset Library is the default view and allows you to view the individual Assets you have on the Platform, select one or more, and directly import them to CLO.
Searching
When viewing the Asset Library, search capabilities allow you to do keyword search from the top search bar for info such as tags, asset name, project name, and attribute keys. You can also filter by Asset Type or Root Project in the left panel.
Preview
When an asset is selected, a preview will also be displayed showing key info on the Asset, attributes, as well as any attachments.
Attachments
When an asset has attachments, you can download/import them while ‘previewing’ the asset, either individually or all at once by clicking the ‘Download All’ button.
Project List
Accessed via the Project List button in the left panel, this view allows you to import assets from specific projects. By default, it will show you the root projects, however clicking one will navigate inside the project and show the next level down, both sub-projects and contained assets. From within a Project, assets can be selected, previewed, and imported the same as from the Asset Library view.
Filetypes and What to Expect
There are a number of filetypes that can be downloaded, however not every filetype will behave the same as when handled manually due to limitations of the API.
Download and Import
The following filetypes can be downloaded and directly imported into VStitcher via the plug-in:
- Garment
- zprj, zpac
- Avatar
- avt, pos, mtn
- Trim
- btn, trm
- Material
- zfab, jpg, jpeg, png, tif, tiff, sbsar
The following filetypes cannot be imported:
- sbs
- xtex
While these cannot be imported directly, the will still be downloaded and the plug-in will open their location in the native file explorer to simplify the process of manually bringing them into CLO.
Additional Notes on Imports
When importing .zprj/zpac files via the API, it will always close any currently open .zprj file. The plug-in will attempt to intelligently determine the order of imports to ensure this doesn’t cause disruption, however trying to import multiple .zprj files will not have the results you expect.
Images will be imported as graphics. If they are needed for materials, they will have to be manually added from the Downloads folder.
Settings
The settings window, accessed via the menu in the upper right corner offers only a couple settings at this time:
- API URL – allows you to set a different base URL for all VNTANA API calls.
- This should only be changed if VNTANA have provided your organization with a private environment for which the API URL would be different. It will not work with any URL associated with your API.
- Logging
- Open Logs – opens the directory on your machine containing log files.
- Enable Debug Logging – Off by default, this will enable verbose logging. Generally not needed, however if an issue occurs we may ask you to run the plug-in with this enabled to troubleshoot.
Plugin Operations and Possible Issues
Avatars
Avatars can cause issues for a number of reasons including missing permissions files, missing or unsupported materials, and inability to properly export due to the need for special export settings. It is generally recommended that if a complex avatar is needed the asset should be processed manually.
Note: For MacOS users, Avatars are not behaving correctly in the CLO API for 7.2. The method needed to show an Avatar allowing for it to be exported is broken. Despite this, it is still recommended that you only use CLO 7.2 with the Plug-in on Mac as there are more problematic issues in earlier versions. To circumvent this, you need to make sure your files have the Avatar set to show before they are run.
Crashing on MacOS
Generally, CLO has some compatibility issues with Mac computers, specifically with the newer M1 chips. This can cause crashes during export, extremely long export times, as well as running out of resources requiring CLO be ‘Force Quit’. If issues occur with the Mac version, please contact our support team at [email protected] to determine if it is a bug in the plugin.
Note: This issue appears to have been fixed with 7.1 and above, but if it still occurs for you please reach out so we can verify the cause.
Miscellaneous Issues
Product Created but no 3D
If you see some of your Products get created during a batch but the 3D asset never gets uploaded, this may be the result of a soft sleep of your computer which can result in an interrupted network computer. This is especially the case on MacOS as these devices will dim the display indicating a reduction in power usage but actually soft sleeps the processes. If you are going to be running larger batches it is best to disable sleeping on your machine.
Note: If none of your 3D are getting uploaded, this may be related to your security blocking calls to Google API’s. See the section below on Communication to see what may need to be white listed by your IT security team.
Missing or Ignored Files
The plugin searches for files in the given directory that are .zprj files. If any of these files contain this extension with any non-lowercase letters (i.e. .Zprj), it will ignore them. This is by design as Clo can behave in unpredictable ways with these files when using the API.
Extra Files
The process by which the plugin searches for .zprj files in the given directory is recursive, meaning it will pull from all subdirectories it reaches. This can lead to projects that aren’t ready to be uploaded being processes if they are accessible via the directory set in the plugin. This generally only causes the inconvenience of having to delete these, but depending on their completeness they can cause unexpected errors.
It is generally recommended to create a single directory to save out ready to process projects to ensure only those that are ready are processed.
How the Plugin Communicates
The plugin makes use of the Python library Requests for all of it’s communications. If you are having trouble simply logging in to the plugin, there is a very high chance that security measures on your workstation are preventing the plugin from making the requests it needs to function. In order to circumvent this, your IT and Security teams will need to decide whether they are comfortable whitelisting everything the Plugin needs to function properly.
The plugin makes use of HTTP for it’s communications and will make calls to a couple of domains that may need to be whitelisted. The two main domains are:
- *.vntana.com – this domain covers the majority of Plug-in functionality from authentication to tag and product creation.
- storage.googleapis.com – this domain is used for the uploading of your 3D assets to the created Products. Without this the Plug-in will only be able to create empty Products without an asset.
Base URL: https://platform.vntana.com
Endpoints:
/v1/auth/login
/v1/auth/login/token
/v1/auth/refresh-token
/v1/organizations
/v1/clients/client-organizations
/v1/clients
/v1/clients/slug-availability
/v1/tags/search
/v1/tags/create
/v1/products/{productUuid}/search * (The productUuid can be different each time)
/v1/products
/v1/storage/upload/clients/products/asset/sign-url
/v1/variant-groups * (Query Parameters will be added to this: ?clientUuid=zzz&name=zzz&organizationUuid=zzz)
/v1/variant-groups/search
/v1/variant-groups/add-products * (Query Parameters will be added to this: ?productsUuids=zz,zz&uuids=zz,zz)
Additional URL
https://vntana-platform-2-development.wl.r.appspot.com/plugin-version-clo
https://vntana-platform-2-development.wl.r.appspot.com/plugin-version-bw (for the BW plugin if that will be used)
Google Signed URL
https://storage.googleapis.com *
Some endpoints pass information in the URL as query parameters and as such will not be the same every time. Additionally, the final endpoint used in the process of uploading an asset to the Platform uses a signed URL generated by Google.
Additional Resources
Authentication Token
An Authentication Token can be generated on the VNTANA Platform to allow secure authentication through the VStitcher and Clo plugins. Once used, this token will allow automatic authentication upon launching either plugin so long as the token isn’t revoked or regenerated, in which case you would simply need to login again through the plugins with a new token to resume automatic authentication.
To generate an Authentication Token, login to the VNTANA Platform and navigate to your profile settings by clicking ‘My Profile’ in the dropdown accessed via your profile picture.
From your profile settings, click on the “Authentication Key” tab, located towards the upper left of the webpage, to access the key generation screen.
The first time you visit this tab you will simply see a button labeled “Generate”, clicking this will generate the Authentication Token for your user account. You can click the copy icon on the right of the generated token to copy it to your clipboard or manually copy it.
As a security measure, you will only be able to copy the token for the first 30 seconds after it is generated. After this time you will have to regenerate a new token the same way should the need arise. Additionally, while a token is active you have the option to revoke it without generating a new one from the same screen.
Compatibility
- Clo 7.1, 7.2, 2025.0 (v2.* only)
- Windows
- MacOS