The 3D modelling apps that actually work on iPhone, iPad and Mac
Shapr3D is the closest thing to real parametric CAD on an iPad or Mac, and it is the right pick for product shapes, mechanical parts and anything that needs precise dimensions rather than a freeform surface. It runs on Apple Pencil but works just as well with a mouse on Mac.
Nomad Sculpt is a digital-clay sculpting app built for organic forms, characters and concept shapes rather than precise dimensions. It produces dense, high-poly meshes that look great in its own viewport but need reduction before they are ready for AR.
uMake takes a sketch-first approach, closer to drawing curves in space with Apple Pencil and letting the app build surfaces from them. It suits concept and industrial design work where the shape is being explored rather than engineered to a tolerance.
Forger is a simpler, more focused iPad sculpting app than Nomad Sculpt, aimed at quick organic modelling without the full toolset, which makes it a fast way to block out a shape before refining it elsewhere.
None of the four exports a finished AR Quick Look file directly. Each hands off an FBX, OBJ or GLB, and that handoff is where an AR-ready model either survives or breaks.
Where the AR export actually breaks
The modelling app rarely gets blamed for an AR file that will not open, but the failure almost always starts at export, not at the modelling stage.
- Format lock-in: assuming an app's built-in AR preview means it exports a working USDZ, when most only export FBX, OBJ or GLB and need a separate conversion step.
- Mesh density: sculpting apps like Nomad Sculpt and Forger export at the density used for close-up sculpting, which is far heavier than AR Quick Look needs.
- Scale mismatch: exporting a model at the wrong real-world unit, so it opens correctly in the modelling app but appears the wrong size entirely once placed in AR.
- Missing or baked-in textures: a GLB or FBX exported without embedded textures opens with a blank grey surface once converted, rather than the material shown in the app.
The export route from Shapr3D, Nomad Sculpt, uMake and Forger to USDZ
Shapr3D's FBX or OBJ export is precise but not AR-ready on its own, so it needs to go through the /fbx-to-usdz/ tool to arrive at the format AR Quick Look actually opens.
Nomad Sculpt, uMake and Forger all export GLB more reliably than they export USDZ directly, which means the more practical route for those three is the /glb-to-usdz/ tool rather than hunting for a native USDZ export option that may not exist in the app version installed.
Before converting either format, check that the model is exported as a single mesh with textures embedded rather than referenced externally, and that the scale is set in real-world units (metres), since AR Quick Look places the model at that literal scale with no correction step afterwards.
- Confirm textures are embedded in the export, not left as separate linked files.
- Confirm the export scale is in metres, matching real-world size, before conversion.
- Merge multiple parts into a single mesh where the app allows it, since AR Quick Look handles one clean object more reliably than several loose pieces.
The file-size budget that decides if it opens in AR Quick Look
A converted USDZ that opens fine on a Mac or in a desktop viewer can still fail on a phone, because AR Quick Look is judged on mobile data, not a Wi-Fi test bench. There is a comfortable range where a model loads instantly, and a heavier range where it stalls, spins or simply refuses to load depending on connection.
Running the converted file through the /ar-model-file-size-optimiser/ tool checks it against that practical budget and reduces texture resolution and polygon count where the sculpt or model was exported denser than AR actually needs. For anything that started life as a Shapr3D parametric model, it is worth a second pass through the /cad-to-3d-prep-checklist/ tool first, to catch scale or geometry issues before they get baked into a heavy, hard-to-diagnose AR file.
- Textures: reduce to the resolution AR Quick Look actually displays at typical viewing distance, not the resolution used for close-up sculpting reference.
- Polygon count: sculpting apps in particular need explicit reduction, since their native density is built for editing, not for a phone-based AR viewer.
- Single conversion pass is not enough: check file size after conversion, not before, since USDZ packaging can add weight the source GLB or FBX did not have.