DevXR

3D freelancers and studios

Present your model. Keep your time for creating it.

Turn a GLB into a client presentation without building a microsite, managing a server or recreating a viewer for every project.

Upload a GLB Test a real model

THE CURRENT WORKFLOW

Invisible delivery work adds up.

Setting up a camera, fixing responsive behavior, hosting assets and redeploying a viewer are necessary tasks, but rarely billable or cleanly reusable.

BEFORE

A fragmented delivery

  1. 01Assemble the viewer
  2. 02Deploy
  3. 03Correct
  4. 04Redeploy

DEVXR

One continuous path

  1. 01Upload
  2. 02Configure
  3. 03Preview
  4. 04Publish

THE TRANSFORMATION

A repeatable presentation, project after project.

The visual Studio centralizes framing, environment, lighting, background, rotation and appearance. Send the result directly or embed it into an existing page.

01

Less one-off development

The viewer, controlled hosting and iframe belong to one workflow.

02

Clear version history

Add notes, archive older versions and choose the active one.

03

Your work comes first

The viewer stays focused and presentation settings are saved with the model.

WORKFLOW EXAMPLE

An agency requests a variation after mobile review.

The studio adjusts the GLB, uploads a new version and reviews it on target devices. The previous version stays in history until the correction is activated.

Open the live demonstration

CLEAR ANSWERS

What DevXR does, and what it does not claim.

Is this a 3D authoring tool?

No. DevXR starts after GLB export to prepare, present, publish and embed the model.

Can I customize the viewer?

Yes for supported scene and appearance settings. Delivery-page branding depends on workspace activation.

Can I provide the source file?

Controlled downloads depend on workspace activation. Arrange source handoff separately while it is not enabled.

ONE MODEL, ONE LINK

Update the version. Keep the client link.

Upload a new version of the same model, wait until it is ready, review its appearance and explicitly select the version to publish. The client keeps the same model URL. A new model creates a separate delivery.

  1. Before sending: verify framing, name, mobile rendering and visibility in a signed-out browser.
  2. During review: identify the version and expected feedback. Comments and approval controls require activation in your workspace; otherwise keep your usual review tool.
  3. After approval: select the reviewed version, test the existing link and retain your source files. A visual approval is not a certified technical or contractual validation.

Check formats, limits and feature availability

Reviewed by DevXR on September 25, 2026.

FAQ

Before your first delivery.

Which settings can I save?

Background, environment, lighting, grid, floor, shadows, reflections, rotation, transform and supported appearance settings.

Does the viewer support AR or VR?

XR paths are available on compatible browsers, hardware and HTTPS contexts. The standard viewer remains the fallback.

Is a React SDK or public API available?

Not as public products at this stage. The current integration method is an iframe.

START WITH A GLB

Deliver your next GLB without a microsite.

Create your workspace and prepare a client presentation in Studio.

Open DevXR Studio