Guides

Deploy a 3D or STL tool

Asset-heavy 3D apps that load glb, gltf, or stl models work out of the box — the kind of build that breaks paste-it-in methods.

3D apps are the stress test for “any build just works.” They load large binary models, use wasm, and reference assets in ways that trip up most paste-it-into-WordPress approaches. App To Page serves them the same way it serves everything else.

3D formats are first-class

App To Page sends the correct content type for the formats 3D apps use, including:

  • glb and gltf — glTF models
  • stl — meshes for printing/visualization
  • wasm — for decoders and physics
  • fonts, textures, and other binary assets

You don’t configure any of this. Upload the build and the right headers go out automatically.

Build it relative

If your tool is built with Vite/React/Three.js, set a relative base so model and texture URLs resolve at your mount path:

// vite.config.js
export default { base: './' };

Make sure your model files ship inside the build output (e.g. in public/ so they land in dist/), and that your code references them relatively.

Upload

  1. npm run build, then zip the contents of dist/.
  2. App To Page → Apps → drop the zip → pick a URL like /models.
  3. Create draft → Preview (load a model to confirm it renders) → Publish.

Live at your-site.com/models, loading .glb/.stl straight from your WordPress site — no separate asset host, no CDN setup.

A 3D configurator is also the most convincing thing to show people. If you’re picking one app to publish first as proof it works, make it this one.