DevXR

3D scanning and photogrammetry studios

Deliver a 3D scan that is ready to review.

Present a survey, digitized object or heritage model in a private-by-default viewer, without asking the client to install your production software.

Upload a GLB Test a real model

THE CURRENT WORKFLOW

A file transfer does not show the quality of the work.

A heavy GLB sent by transfer provides no framing, consistent lighting or indication of what a phone will load. A video removes freedom to inspect.

BEFORE

A fragmented delivery

  1. 01Clean the scan
  2. 02Compress by guesswork
  3. 03Transfer the file
  4. 04Collect feedback by email

DEVXR

One continuous path

  1. 01Upload
  2. 02Measure
  3. 03Prepare
  4. 04Present

THE TRANSFORMATION

From raw survey to a controlled web version.

The pipeline checks the GLB container, measures geometry and textures where possible, then produces a processed version without replacing the validated original.

01

Measurable diagnostics

Compare size, vertices, triangles and textures before and after processing.

02

Non-destructive versions

Keep the validated original and explicitly activate a ready derived version.

03

Accessible review

The client opens the viewer on desktop or mobile and inspects the result freely.

WORKFLOW EXAMPLE

A heritage scan needs review before final delivery.

The studio uploads the cleaned GLB, reviews its indicative score, configures neutral lighting and shares the published version. After changes, a new version can be compared before activation.

Open the live demonstration

CLEAR ANSWERS

What DevXR does, and what it does not claim.

Does the score guarantee performance?

No. The Web Readiness Score is a technical estimate that should be supplemented with target-device testing.

Does DevXR support point clouds?

No. The current scope is GLB and supported FBX after conversion to validated GLB; convert DWG with a suitable tool before upload.

Is optimization lossless?

Several profiles exist. No profile guarantees identical rendering on every device; always review the output.

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.

What is the maximum upload size?

The Free plan allows up to 100 MB per file; limits depend on your plan and service configuration. Check the plans and limits page.

Is the original retained?

Yes. The validated original is kept separately from the processed version.

Can I compare versions?

Yes. Studio can compare metrics between two versions before activation.

START WITH A GLB

Test with a representative scan.

Evaluate the workflow using a GLB close to your usual deliveries.

Open DevXR Studio