Why AR isn't launching on your Shopify store (and how to fix it)

A customer taps “View in your space” on your Shopify product page, holds up their phone — and nothing happens. The camera opens, the product never appears, or the browser quietly returns to the regular page view. Your 3D investment just failed at the moment that matters most.

AR launch failures on Shopify are common enough that many merchants assume it's a platform bug. It usually isn't. The cause is almost always the model — and it is fixable.

The primary cause: file size

More than 90% of Shopify AR failures trace back to model file size.

Shopify's “View in your space” uses AR Quick Look on iOS (Safari) and Google Scene Viewer on Android Chrome. Both engines download and process the model before they can show it in AR. If the download takes too long — or if the model exceeds the internal memory budget that triggers a silent abort — AR never launches. No error message is shown to the customer. The button simply does nothing.

Shopify officially recommends models under 15 MB. In practice, AR Quick Look is unreliable above 10–12 MB on older iPhones, and frequently fails on mid-range Android phones above 8 MB. For reliable AR across your full customer base — which skews heavily towards mid-range devices — the realistic target is 4–5 MB.

A 22 MB furniture model will not launch AR on an iPhone 12 over 4G. Not intermittently — never.

iOS vs. Android: how failure looks different

Understanding the platform difference helps narrow the cause when testing:

iOS (AR Quick Look via Safari):AR Quick Look runs in Safari's native WebKit layer. It downloads a USDZ file — which Shopify automatically generates from your GLB. If the USDZ conversion fails due to file size, model complexity, or an unsupported texture format, the AR button silently does nothing when tapped. There is no error message to the user. Check file size and texture formats first.

Android (Google Scene Viewer): Scene Viewer downloads the GLB directly. If the file is large or the network is slow, the viewer may show a prolonged loading state before quietly exiting. On older Android devices with limited RAM, models above 8 MB are unreliable regardless of network speed.

If AR fails on iOS but works on Android (or the reverse), the issue is more likely format-related than file-size-related.

Other causes to check

Once file size is within range, check these in order:

• Wrong base format. Shopify expects a GLB for the 3D viewer. It auto-generates a USDZ from the GLB for iOS AR Quick Look. If the GLB is broken, uses unsupported extensions, or has malformed geometry, the USDZ conversion fails silently — and iOS customers get nothing. Run the GLB through the MeshGrade analyzer to check for format issues.
• Too many materials or draw calls. AR Quick Look has documented limits on scene complexity. A model with 80+ materials and 200+ meshes may load fine in the desktop viewer but crash or freeze in AR on devices with limited memory. The analyzer reports draw calls and material count so you can see whether this applies.
• Unsupported texture formats. Some exporters embed HDR or non-standard texture formats. AR Quick Look is stricter than most desktop renderers about texture format compliance. The analyzer flags textures that fall outside supported formats.
• Non-standard glTF extensions. Models using draft or vendor-specific glTF extensions may parse in Three.js but fail in the iOS WebKit AR pipeline, which follows the glTF spec more closely. Validate the GLB with the official glTF Validator if format-level failures are suspected.

How to diagnose

The fastest way to identify the cause is to run the model through MeshGrade. It runs in your browser, requires no upload, and reports:

• File size vs. the 15 MB Shopify target
• Triangle and vertex counts vs. the 100k triangle target
• Draw calls and material count
• Every texture with its resolution, format, and estimated VRAM
• Any flagged glTF format issues

The grade report tells you whether the problem is file size (the most common case), draw calls, textures, or something else — without guessing.

What to fix first

Fix in this order:

1. File size. Compress textures to KTX2 and apply Draco geometry compression. These two changes together typically reduce most models from 20+ MB to 3–5 MB.
2. Triangle count. If above 100k, decimate the mesh. 50–80k triangles is the reliable zone for mobile AR on product models.
3. Draw calls. Merge meshes that share a material. Reduce material count by consolidating similar materials with a texture atlas. Aim for under 20 draw calls.
4. Format issues. If the above are all within range and AR still fails, validate the GLB and check whether textures use standard formats (JPEG, PNG, or KTX2).

Before and after: furniture model

A furniture model graded on MeshGrade arrived at 22 MB and 480,000 triangles — grade D. AR Quick Look failed on every iPhone used for testing.

After optimization:

• File size: 3.4 MB (85% smaller)
• Triangles: 70k (85% fewer)
• AR result: launches instantly, reliable across device types

The silhouette and material quality were unchanged. The only visible difference was that AR worked.

Start with a free grade

Grade your model free → — runs in your browser, no upload, no sign-up. You'll get a Shopify-benchmarked score and a prioritized list of what is causing the AR failure. Most AR issues are fixable within a few hours.