Frequently asked questions

What Blendspace accepts, what it produces, how the viewer and AR work, and where your files live.

Getting started

What does Blendspace actually do?

You upload one 3D file. Blendspace converts it to the two formats the web needs (GLB and USDZ), stores them, and gives you an HTML snippet you paste into a product page. Visitors get an interactive 3D viewer, and on a phone they can place the product in their own room in AR.

Do I need to know anything about 3D to use it?

No. The conversion, the AR packaging and the viewer configuration are handled for you. You need a 3D file of your product and the ability to paste an HTML snippet into your storefront, or to install the Shopify or WooCommerce plugin, which removes the copy-paste step entirely.

Where do I get 3D models of my products?

Three routes. Export from CAD or a 3D suite if your products are already modelled, commission a scan or a model, or use the experimental photo-to-3D feature that generates a model from a single product photo.

Can I try it before paying?

There is a live demo on the site that runs the same viewer and AR path a paying customer gets. It is the real pipeline, not a video.

File formats and conversion

Which file formats can I upload?

FBX, GLB, GLTF, OBJ and USDZ. You can also upload a ZIP archive containing several of those files and they are processed together.

What do I get back?

Every accepted upload produces both a GLB and a USDZ. If you upload a GLB, the original is kept and only the USDZ is generated, and the same applies in reverse for a USDZ upload.

Why do I need two output formats?

Because iOS and Android take different paths to AR. iOS uses Quick Look, which requires USDZ. Android uses Scene Viewer, which reads GLB. Serving only one format means AR silently fails on half of your visitors.

How large can an uploaded file be?

The upload endpoint accepts files up to 50 MB. Conversion also has a time budget, so a very dense mesh can fail even under the size limit. Decimating the mesh and keeping textures at 2K resolution is the usual fix, and it makes the model load faster on a product page anyway.

Are materials and textures preserved?

PBR materials survive conversion. Two glTF material extensions, KHR_materials_specular and KHR_materials_ior, are deliberately stripped from the GLB output because they break rendering in viewers with limited extension support, macOS Quick Look in particular. The base colour texture carries the appearance instead.

What about animations and rigging?

Blendspace targets static product presentation. Treat animation and rigging as unsupported and export a static pose.

My conversion failed. What now?

The most common causes are an unsupported extension, a file over the size limit, textures referenced by an absolute path that is not in the archive, and meshes dense enough to exhaust the conversion time budget. Re-exporting as GLB from your 3D tool with textures embedded resolves most cases.

Embedding and AR

How does the embed work?

You get an iframe snippet pointing at a hosted viewer page. Paste it into your product template. There is nothing to build, no npm package, and no script tag to maintain.

What renders the 3D model?

Google’s model-viewer web component, version 4.0.0. It is the same component used across a large part of the e-commerce 3D ecosystem, so behaviour is predictable and well documented.

Which AR modes are supported?

WebXR, Scene Viewer and Quick Look. The viewer picks whichever the visitor’s device supports, so iPhones get Quick Look, Android phones get Scene Viewer, and headsets and WebXR-capable browsers get WebXR.

Does AR work on desktop?

Desktop visitors get the interactive 3D viewer, which they can rotate and zoom. AR placement needs a phone or headset camera, so the AR button only appears on devices that can honour it.

Is there a Shopify or WooCommerce integration?

Both. Shopify is covered by an admin app plus a Theme App Extension block you add to the product page in the theme editor. WooCommerce and WordPress are covered by a plugin that provides a shortcode, a Gutenberg block and WooCommerce product integration. The WordPress plugin requires WordPress 6.0 or newer and PHP 8.0 or newer.

What does the WordPress shortcode look like?

The shortcode is blendspace_3d and it takes a model_id attribute plus an optional height. The Gutenberg block wraps the same rendering if you prefer the editor.

Plans, limits and billing

How many models can I host?

The plan sets the ceiling. Small allows up to 10 assets, Medium up to 20 and Large up to 50. Current prices are on the pricing section of the home page.

Can I change plan later?

Yes. Billing runs through Stripe and plans can be changed. Monthly and yearly billing are both available, with yearly costing less per month.

What happens to my models if I cancel?

Cancelling ends the subscription and the associated hosting. Export anything you want to keep before you cancel, because delivery stops when the plan does.

Data, privacy and reliability

Where are my files stored?

Uploaded sources and converted outputs live in Azure Blob Storage, with model metadata in MongoDB. Delivery is over a CDN so viewers load from a location near the visitor.

Do you offer a Data Processing Agreement?

Yes. A DPA for business customers is published on the site alongside the privacy policy, the terms and the cookie policy.

Who operates the service?

Blendspace is a product of Blendlens s.r.o., a Czech limited liability company, company ID 19332351, registered at Tovární 1112, 537 01 Chrudim, Czech Republic. Full legal identification is on the imprint page.

Still stuck?

Write to info@blendspace.io. If the answer turns out to be useful to more than one person, it ends up on this page.