3D File Formats for E-Commerce

3D product models are not a novelty feature. They directly affect conversion rates and return rates. Shopify reports that products with 3D models see up to 94% higher conversion rates compared to static images alone. Amazon's internal data shows a 2x conversion increase for products with "View in 3D" enabled and a 20% reduction in returns for items viewed through AR.

The reason is straightforward: customers can rotate the product, zoom into details, and place it in their own space through augmented reality. They make more confident purchases because they understand the product better before buying.

Google is also factoring 3D into product search results. Listings in Google Merchant Center that include a 3D model can display an interactive "View in 3D" button directly in search results on Android devices. This gives those listings a visual advantage over competitors showing only flat photos.

The challenge is not whether to add 3D to your store. The challenge is getting the file format right for each platform.

This table covers the verified specifications from each platform's official documentation as of early 2026. Bookmark this page and check back, because these numbers change as platforms update their support.

Despite the dozens of 3D file formats that exist, only two matter for e-commerce: GLB and USDZ.

GLB (GL Transmission Format Binary) is the universal standard for 3D on the web. It packs geometry, textures, materials, and animations into a single binary file. Every major platform accepts it: Shopify, Amazon, Google, WooCommerce plugins, and all modern web browsers. GLB is maintained by the Khronos Group, the same organization behind WebGL and OpenGL.

USDZ (Universal Scene Description) is Apple's format for augmented reality. When an iPhone or iPad user taps "View in AR" on a product page, Safari opens the USDZ file in AR Quick Look. No app download is needed. USDZ is a zip archive containing a USD scene file and its textures in a single package, designed by Apple and Pixar for zero friction AR experiences.

If your 3D models are in FBX, OBJ, STL, or any other format, you need to convert them to GLB (and optionally USDZ) before uploading to any e-commerce platform. None of the major platforms accept source formats directly. Polyforge's converter handles this in the browser without uploading your files to any server.

Shopify has the most mature 3D product support among e-commerce platforms. Every Shopify plan includes a built-in 3D viewer and AR support at no extra cost.

Required format: GLB. Upload a GLB file through Products > Media in Shopify admin. Shopify automatically converts GLB uploads to USDZ for iOS AR, so you only need to upload a single GLB file. Shopify routes the correct format to each device automatically: GLB for web browsers and Android, USDZ for iPhones and iPads.

File size: Shopify accepts uploads up to 500 MB. Files over 15 MB are automatically optimized, but the quality may suffer. For the best mobile performance, aim for under 5 MB. Models under 4 MB load noticeably faster on cellular connections.

Polygon count: Shopify recommends staying under 100,000 polygons. There is no hard technical limit, but exceeding 100K can cause sluggish rotation on older phones and tablets.

Textures: Maximum resolution is 2048 x 2048 pixels, but 1024 x 1024 is preferred to keep file size down. Use JPEG for textures without transparency. Switch to PNG only when you need an alpha channel. Shopify expects PBR (Physically Based Rendering) materials using the metallic roughness workflow: pack occlusion into the red channel, roughness into green, and metalness into blue of a single texture.

Plan limits: Starter and Basic plans allow 250 3D models per store. Grow allows 1,000. Advanced allows 5,000. Shopify Plus has custom limits.

Amazon supports 3D models through its "View in 3D" and "View in Your Room" features, but access is more restricted than on Shopify. You must be enrolled in Amazon Brand Registry to upload 3D models. This requires a registered or pending trademark.

Required format: GLB only. Amazon does not accept USDZ, FBX, OBJ, or other formats for product listings.

File size: Maximum 5 MB. This is the strictest limit among major platforms. Models larger than 5 MB will be rejected during upload.

Polygon count: Maximum 20,000 triangles. This is a hard limit, not a recommendation. Amazon enforces it during their quality review process. A 20K triangle budget is tight. Plan for it during modeling, not as an afterthought.

Textures: Maximum 1024 x 1024 pixels per texture. PNG or JPEG only. PBR materials are recommended for realistic appearance, but keep texture files small to stay within the 5 MB total limit.

Animations: Not supported. Amazon's 3D viewer only handles static models. Do not include animation data in your GLB file.

Eligible categories: Not all products qualify. Supported categories include furniture, home decor, consumer electronics, shoes, eyewear, toys, and appliances. The list varies by region and is expanding.

Review process: After uploading through Seller Central (Catalog > Image Manager), Amazon reviews the model for quality. Include 2 to 10 reference photos and accurate product dimensions with your submission. Expect the review to take several days to two weeks.

Google supports 3D models in product search results through Merchant Center. When a user searches for a product on an Android device, they can tap "View in 3D" to inspect the model interactively, and "View in your space" to place it in their room through AR.

Required format: GLB or glTF. Google uses the virtual_model_link attribute in your Merchant Center product feed to reference the 3D model file URL.

File size: Recommended under 10 MB. Maximum 15 MB. The model file must be served over HTTPS.

Polygon count: Google recommends under 100,000 triangles for Scene Viewer, which powers the AR experience on Android. For Display and Video 360 campaigns, keep models under 12,000 polygons.

Textures: Maximum 2048 x 2048 pixels per individual texture. PNG or JPEG only, in sRGB color space. Maximum 10 materials per model. A model can have at most 1 UV map per mesh and up to 254 bones for rigged models.

Supported glTF extensions: Google officially supports KHR_materials_unlit and KHR_texture_transform. Using unsupported extensions will trigger validation errors in Merchant Center. Check your GLB with Google's Scene Viewer validator before submitting.

Animations: Supported. Scene Viewer plays the first animation in the file automatically and loops it. If your model contains multiple animations, only the first one will play.

Geographic availability: Currently available in the US, Australia, Canada, Japan, and India.

Structured data: For search integration, add schema.org/3DModel markup to your product pages. Link the 3D model using the subjectOf property on your Product schema. This helps Google discover and index the 3D model alongside your product listing.

Apple's AR Quick Look lets iPhone and iPad users view 3D products in their real environment directly from Safari. No app is needed. It has been available since iOS 12 and works on iPhone 7 and later, iPad 5th generation and later, and all iPad Pro models.

Required format: USDZ exclusively. This is a zip archive (uncompressed, unencrypted) containing a USD scene and its texture files. The MIME type must be set to model/vnd.usdz+zip on your server for Safari to recognize it.

File size: Apple does not publish a hard limit, but recommends keeping files between 4 and 8 MB for fast AR loading. Apple's own showcase models typically weigh around 4 to 5 MB.

Polygon count: Recommended maximum of 100,000 polygons. Complex models beyond this threshold can cause frame drops during AR rendering on older devices.

Textures: Recommended resolution of 1024 x 2048 or 2048 x 2048 pixels. Always use power of two dimensions (512, 1024, 2048). Supported image formats inside the USDZ archive are PNG, JPEG, OpenEXR, and AVIF. Use sRGB color space for base color textures and linear color space for all other maps.

Materials: USDZ uses USD Preview Surface, a metallic roughness PBR system. Supported maps include base color (diffuse), metallic, roughness, normal, ambient occlusion, and emissive. Normal maps must use OpenGL tangent space with the green channel pointing up.

Apple Pay integration: AR Quick Look supports in-AR purchasing through Apple Pay. Add URL fragment parameters to your USDZ link: product.usdz#checkoutTitle=Product&price=99. This displays a purchase button directly in the AR experience. One limitation: these parameters only work with direct file URLs, not blob URLs generated by JavaScript.

HTML implementation: Trigger AR Quick Look with a simple anchor tag: <a href="model.usdz" rel="ar"><img src="preview.jpg"></a>. The rel="ar" attribute is required, and an <img> must be the first child element inside the link.

Apple Vision Pro: With visionOS 26, Apple introduced the HTML <model> element for spatial web content. This allows 3D product models to be embedded directly in web pages for interactive viewing on Vision Pro without leaving the browser.

If you run a WooCommerce store or a custom built shop, you are not locked into a single platform's 3D viewer. The most common approach is Google's open source model-viewer web component, which works in all modern browsers and provides built in AR support on both Android and iOS.

Format: GLB is the standard for model-viewer and all major WordPress 3D plugins (Easy 3D Viewer, AR Model Viewer for WooCommerce, Visody 3D Product Viewer). For iOS AR, model-viewer can automatically serve a USDZ file as a fallback when you provide one alongside the GLB.

Recommended specs: Keep GLB files under 10 MB and polygon counts under 50,000 triangles. There is no enforced limit since you control the hosting, but these numbers ensure smooth performance across devices. Textures at 1024 x 1024 pixels offer the best balance between quality and loading speed.

Browser support: model-viewer works in the last two major versions of Chrome, Firefox, Safari, and Edge. WebXR AR features work on ARCore devices (Android) and fall back to AR Quick Look on iOS when a USDZ file is provided.

Snapchat integration: For AR commerce through Snapchat Lenses, Lens Studio accepts GLB, FBX, and OBJ files. Standard meshes must stay under 100,000 triangles. Rigged meshes (for virtual try on) have a tighter 60,000 triangle limit. The entire lens package, including the 3D model, textures, and lens logic, must be under 8 MB total.

Regardless of which platform you target, the preparation process follows the same steps. Start with the strictest platform's requirements (Amazon at 5 MB and 20K triangles) and create higher fidelity variants from there.

1. Convert to GLB first. If your source model is in FBX, OBJ, DAE, or any other format, convert it to GLB before doing anything else. GLB is the baseline format that every platform accepts. Polyforge's converter handles all common source formats.

2. Reduce polygon count. Use decimation to bring the triangle count within your target platform's budget. For Amazon, that means 20K or fewer. For Shopify and Google, 100K or fewer. For the widest compatibility, aim for 50K or fewer. Polyforge's optimizer includes polygon reduction that runs entirely in your browser.

3. Optimize textures. Resize textures to 1024 x 1024 pixels for maximum compatibility. Convert PNG textures to JPEG where transparency is not needed. This alone can cut file size by 50% or more. Use power of two dimensions (512, 1024, 2048) because WebGL and mobile GPUs require them for proper mipmap generation.

4. Check PBR materials. All platforms expect metallic roughness PBR materials. If your model uses the older specular glossiness workflow, convert it before uploading. Most 3D tools (Blender, Substance Painter) export metallic roughness by default when targeting glTF/GLB.

5. Remove unnecessary data. Strip out cameras, lights, empty nodes, invisible geometry, and unused materials. These add to file size without contributing to the viewer experience. FBX files from Maya and 3ds Max are especially prone to carrying editor state and metadata.

6. Create the USDZ variant. If you need iOS AR support (Shopify, Apple Quick Look, or any site using model-viewer), convert your optimized GLB to USDZ. Polyforge's GLB to USDZ converter produces USDZ files directly in the browser.

7. Validate before uploading. Test your GLB in a viewer like model-viewer.dev. Test your USDZ by opening it on an actual iPhone or iPad. For Google Merchant Center, run the file through Google's Scene Viewer validator. Catching issues before upload saves days of back and forth with platform review teams.

Beyond file specs, each platform differs in features and access requirements. This table helps you decide where to invest your 3D effort first.