3D apps are the real stress test for “any build just works.” They load large binary models, lean on
wasm, and reference assets in ways that trip up most ways of putting an app into WordPress. App To
Page serves them the same way it serves everything else — so a Three.js viewer or an STL generator
runs at your URL with nothing special to set up.
The Voronoi Wall Designer in our showcase is exactly this kind of app.
3D file types are first-class
App To Page sends the correct content type for the formats 3D apps rely on, including:
glbandgltf— glTF models.stl— meshes for 3D printing and visualization.wasm— for decoders, physics, and mesh processing.- Fonts, textures, and other binary assets.
You don’t configure any of this. Upload the build and the right headers go out automatically — which is what most “paste the code into a page” approaches can’t do.
Build with a relative base
If your tool is built with Vite, React, or Three.js, set a relative base so your model and texture URLs resolve at the URL where the app is mounted:
export default { base: './' };Two things to double-check for 3D apps specifically:
- Bundle your models with the build. Put model and texture files where your build includes them
(for example in
public/, so they land indist/), and reference them relatively in code. - Keep large assets inside the zip. If a model lives outside the folder you zip, it won’t be there to serve.
Upload it
- Run
npm run build, then zip the contents ofdist/. - Go to App To Page » Apps and drop the
.zip. - On the Confirm your app card, pick a URL like
model-viewer, set who can view it, and tick the trust checkbox. Click Create draft. - Click Preview and load a model to confirm it renders, then Publish.
It’s live at your-site.com/model-viewer, loading .glb and .stl files straight from your WordPress
site — no separate asset host and no CDN to configure.
Frequently asked questions
Can you host a Three.js or WebGL app on WordPress?
Yes. Build it for production with a relative base and upload the build. App To Page serves the HTML,
JavaScript, wasm, and 3D model files with the correct content types, so it runs at your URL like it
does locally.
Does it serve STL and glTF files correctly?
Yes. stl, glb, and gltf are served with the right content types automatically — no .htaccess
edits or MIME-type configuration needed.
My models are large. Is that a problem?
No. Large binary models are served directly and cached, so repeat loads are fast. Just make sure the model files are inside the zip you upload.
Why do 3D apps break with other methods?
Pasting an app into a page or a block usually can’t serve wasm or 3D model files with the right
content types, and it wraps your app in the theme. App To Page serves the raw files standalone, which
is why asset-heavy 3D tools work.