CAD, glTF and GLB product assets
3D product configurator asset pipeline.
Turn authoritative CAD, drawings and 3D source models into browser-ready product assets. Plan scale, materials, moving parts, product-data binding and acceptance around the products your customers configure.

Connect visual detail to a governed product record.
Product and engineering ownership
Engineering CAD can define construction. A product data model can define valid choices, identifiers and commercial meaning. A pricing engine can define calculations; a BOM or production service can define components and operations. The 3D scene communicates that accepted state and stays connected to those owners.
A versioned connection
Each visible finish, accessory, dimension, module and motion maps to a stable product identifier and explicit behavior. The same saved configuration can then drive the view, price, quote, approval, materials and project handoff without relying on screen labels or scene-tree order.
Controlled source and derivative
glTF is a runtime delivery format complementary to authoring formats. Preserve editable and authoritative sources, derive the customer-facing asset deliberately, validate the published artifact and retain the mapping that gives the geometry its product meaning.
Define the pipeline before estimating the model.
Choose the starting source, product behavior and primary delivery target. The outline identifies work to include in a supplier brief. It is a planning aid; time, price and engineering acceptance require your actual catalogue and devices.
Choices change this outline on the page. They do not submit an enquiry or save a project.
Planning scope
Advanced pipeline
Planning scope: Advanced pipeline. Require source, behavior, mobile/AR, performance, revision and end-to-end trace evidence.
Require source, behavior, mobile/AR, performance, revision and end-to-end trace evidence.
- Extract a customer-visible derivative from authoritative CAD
- Remove manufacturing-only and hidden detail
- Rebuild runtime hierarchy, topology, UVs and materials
- Separate validated dimensions from generated visual geometry
- Reconcile repeated quantities and output measurements
- Test minimum, maximum and coupled boundary configurations
- Prioritize first usable view, touch behavior and memory
- Test variable networks and sustained option changes on real phones
- Starting source
- Engineering CAD
- Product behavior
- Made-to-measure system
- Primary target
- Public mobile web
Ten stages from source to accepted release.
Stages can overlap. Keep an owner, input, work definition and evidence for each handoff so visual quality remains connected to product accuracy and web performance.
01Source auditProduct engineering + 3D lead
Identify the authoritative source for shape, dimensions, finish, naming and behavior. Separate construction detail from customer-visible detail and list every configurable state before conversion begins.
- Input
- CAD assemblies, drawings, finish samples, existing models and product identifiers
- Evidence
- Source register, revision, scope map and named approval owners
02Units, axes and origin3D lead
Normalize units, up axis, forward direction, local origins, floor contact and assembly reference points. A model that looks correct but has the wrong scale or pivot will fail measurement, animation, snapping and AR.
- Input
- Accepted scale, orientation and placement rules
- Evidence
- Known-dimension check, bounding box and origin screenshot
03Geometry and topology3D artist + configurator engineer
Remove invisible manufacturing detail, repair normals, simplify curves, control triangulation and preserve silhouettes, joints and moving surfaces. Split geometry by real behavior—not arbitrary authoring groups.
- Input
- Approved visible forms and behavior map
- Evidence
- Viewport comparison, geometry statistics and deformation tests
04Hierarchy, pivots and naming3D lead + product-data owner
Create stable nodes for moving, replacing, hiding, measuring and selecting parts. Name nodes, materials and animation clips with governed IDs so runtime code does not depend on an artist's temporary labels.
- Input
- Product part IDs and interaction requirements
- Evidence
- Node manifest, pivot checks and identifier mapping
05UVs and PBR materialsMaterial artist + brand owner
Build consistent UVs and physically based material inputs for base color, roughness, metallic behavior, normals, ambient occlusion, emissive surfaces and transparency where required. Approve appearance across the actual lighting environments.
- Input
- Physical samples, finish codes and approved references
- Evidence
- Material library, texture inventory and reference-scene comparison
06Runtime optimization3D engineer + web performance owner
Reduce unnecessary vertices, draw calls, materials, texture memory and shader complexity. Evaluate instancing, levels of detail, texture resizing, mesh compression and KTX 2.0 delivery as measurable choices—not automatic checkboxes.
- Input
- Representative products, devices, browsers and networks
- Evidence
- Before-and-after network, decode, memory and frame measurements
07Product-data bindingConfigurator engineer + product owner
Map every visual state to governed product meaning. Specify whether a choice swaps material, changes visibility, transforms a node, replaces a module, instances a component or drives generated geometry.
- Input
- Stable option, component, material and rule identifiers
- Evidence
- Binding manifest and option-to-visual trace tests
08Export and validation3D pipeline owner
Publish the delivery asset, validate glTF structure and extensions, confirm dependencies, inspect warnings and prevent unsupported authoring data from silently disappearing during export.
- Input
- Approved export profile and supported runtime extensions
- Evidence
- Validator report, export log, dependency manifest and checksum
09Scene and behavior QAQA + product + 3D owners
Test materials, options, dimensions, moving parts, camera framing, collisions, clipping, transparency, shadows, saved projects and incompatible combinations across the supported runtime matrix.
- Input
- Acceptance scenarios and reference configurations
- Evidence
- Passed scenario pack with screenshots, configuration IDs and device results
10Publishing and revision controlProduct operations
Publish an immutable revision, connect it to compatible product-data revisions and retain rollback. Treat a model replacement as a governed product change when it can affect options, saved projects or outputs.
- Input
- Accepted asset, bindings and release record
- Evidence
- Release ID, compatible revisions, asset hash, approval and rollback result
Source and delivery formats have different roles.
Retain the editable or engineering source. Publish a runtime derivative suited to the browser and record how it was created so the process can be repeated when the product changes.
CAD and engineering formats
Source and manufacturing intent
Review format responsibilities
- What it can preserve
- Precise assemblies, parametric features, tolerances and construction detail
- Pipeline decision
- Usually too detailed, authoring-specific and structurally unsuitable for direct browser delivery
DCC authoring formats
Visual authoring and exchange
Review format responsibilities
- What it can preserve
- Editable meshes, modifiers, rigs, material authoring and high-quality source textures
- Pipeline decision
- Preserve as controlled source; export only supported runtime behavior
glTF (.gltf)
Runtime 3D scene delivery
Review format responsibilities
- What it can preserve
- JSON scene description with referenced buffers and images, useful when separate resources are intentional
- Pipeline decision
- Dependencies, caching and deployment paths must stay complete and versioned
Binary glTF (.glb)
Compact runtime delivery
Review format responsibilities
- What it can preserve
- A single binary container can package scene data, geometry and embedded resources
- Pipeline decision
- One file is operationally convenient, but product binding and performance still require validation
KTX 2.0 textures
Portable GPU texture delivery
Review format responsibilities
- What it can preserve
- Compressed texture payloads designed to reduce transfer and GPU memory across platforms
- Pipeline decision
- The runtime must support the selected glTF extension and transcode path
Draco or meshopt geometry compression
Compressed mesh delivery
Review format responsibilities
- What it can preserve
- Reduced geometry transfer size for supported loaders
- Pipeline decision
- Measure decoder cost, compatibility and total time to first usable interaction
Six ways a configuration becomes visible.
Choose the behavior that communicates the accepted product choice. Materials, visibility, transforms, modules, instances and generated geometry have different responsibilities. Keep their product identities traceable.
Material assignment
Frame color, wood stain, fabric, powder coat, worktop or panel finish
Binding contract
Product finish ID → governed material ID → runtime material slot
A visually similar color can still be the wrong commercial or production finish.
Visibility state
Optional screen, light, handle, support, appliance, glazing panel or cover
Binding contract
Option state → component ID → visible node set
Hidden geometry must not continue to affect measurements, collisions or BOM logic unless intended.
Transform and animation
Opening louvres, sliding doors, extending awnings and moving mechanisms
Binding contract
Allowed state or parameter → pivot/clip → bounded transform
Animation communicates behavior; it must not imply unsupported travel, clearance or mechanics.
Module replacement
Post types, roof modules, cabinet units, doors, appliances and equipment options
Binding contract
Compatible component ID → asset/node revision → connection interface
Replacement parts need stable connection points, scale, interfaces and downstream identity.
Instanced repetition
Louvers, slats, fence panels, shelf bays, façade modules and repeated fixings
Binding contract
Quantity and spacing rule → component ID → instance transforms
The visible count must reconcile with configuration, price and production quantity.
Procedural geometry
Made-to-measure frames, infills, panels, worktops, roofs and cut profiles
Binding contract
Validated dimensions → geometry generator version → output measurements
Visual generation cannot become an ungoverned second rules or engineering engine.
Define the asset-delivery record.
A machine-readable manifest connects the runtime file to its source, product identity, dependencies and validation. Agree the fields and record actual results for the release being tested.
- Asset and delivery identity
- Record the stable asset ID, immutable revision, delivery URI, media type and full checksum of the exact file being released.
- Source and export profile
- Identify the authoritative source system, product revision, source ownership, conversion settings and reproducible export profile.
- Units and coordinates
- glTF 2.0 uses metres, +Y up and +Z as the asset front. Document source-axis conversion, local origins, floor or wall contact and known-dimension checks.
- Product bindings
- List governed material, component, node, attachment and animation identifiers, including how each permitted configuration changes them.
- Compatibility and dependencies
- Declare compatible product-data, binding-schema and viewer revisions. Include external buffers, images, decoders and required extensions with their delivery paths.
- Validation and release decision
- Attach the actual validator findings, device measurements and scenario results. Record the named reviewers, real approval decision and release time after those checks; retain rollback information.
Measure the complete path to useful interaction.
File bytes are one measure. Include transfer, decode, scene construction, memory, rendering and first interaction. Compare representative products and the largest valid scene on the accepted devices.
Transfer
Asset bytes by geometry, texture, environment and code dependency
What must cross the network before the customer sees and uses the first valid product?
Decode and parse
Compression decoder, image transcode, glTF parsing and scene construction time
Did smaller transfer create a larger main-thread or low-end-device delay?
GPU memory
Texture dimensions, mipmaps, render targets, geometry buffers and duplicate resources
Does the representative scene remain stable on the supported mobile device set?
Render work
Draw calls, triangles, material switches, shader work, transparency and shadow cost
Does interaction stay responsive in the largest accepted valid configuration?
First usable view
Time until a meaningful product is visible and configuration controls respond
Can loading be staged without presenting an incomplete or misleading product state?
Sustained interaction
Frame stability, input delay, thermal behavior and memory over a real selling session
Does the experience remain usable after repeated option changes, saves and scene transitions?
Coordinate convention
The front of a glTF asset faces +Z in its right-handed coordinate system; linear distances are in metres. Keep source transforms, placement and viewer camera conventions explicit rather than assuming every authoring tool uses the same axes.
Loader prerequisites
The delivery profile must match the viewer. Three.js GLTFLoader uses a configured Draco loader for Draco-compressed geometry, a KTX2 loader for compressed textures and a meshopt decoder where required. Test the deployed loader version, required extensions and decoding paths on the supported targets.
A measured budget
There is no universal triangle or texture budget. Set targets using representative devices, browsers, networks, normal products and the largest valid scene. Record transfer, decoder work, memory, drawing cost and interaction while preserving the detail needed for a buying decision.
Eight failures to prevent before launch.
A beautiful model with no product identity
Nodes and materials are named by appearance or export order, so options cannot bind reliably and revisions silently break the configurator.
Control: Use stable product, component and material IDs in a versioned binding manifest.
CAD detail delivered to the browser
Threads, fixings, seals, internal cavities and manufacturing geometry inflate transfer, memory and render work without improving the buying decision.
Control: Preserve authoritative CAD separately and derive a purpose-built customer model.
One file for every possible variant
The asset library explodes as dimensions, colors and accessories are pre-baked into combinations that are difficult to govern and cache.
Control: Separate material, visibility, module, transform, instance and procedural responsibilities.
Wrong scale, origin or pivot
The product appears correct in a preview but fails dimension overlays, snapping, animated motion or placement at real-world scale.
Control: Validate a known measurement, bounding box, floor contact and every interactive pivot.
Textures optimized by eyesight alone
Large maps, duplicated images and inconsistent texel density consume memory; aggressive downsizing makes key finish differences untrustworthy.
Control: Budget by surface importance and target device, then compare physical and approved digital references.
Compression treated as performance proof
A smaller file is celebrated while decoder time, texture transcode, scene construction and first interaction become slower on target devices.
Control: Measure the complete path from request to useful interaction with and without the chosen technique.
Visual rules diverge from commercial rules
The viewer can show a combination that pricing, BOM or production does not recognize—or hide a component that still appears downstream.
Control: Drive every surface from the same accepted configuration state and trace sample states end to end.
Asset replacement breaks saved projects
A new export removes or renames bindings used by earlier configurations, quotes, screenshots or product revisions.
Control: Publish immutable asset revisions, define compatibility and test saved-project reopening before release.
Twelve checks for an asset acceptance pack.
Run these checks against identified assets, product-data revisions, runtime releases and devices. Record results and owners; a screenshot alone does not establish scale, binding or revision compatibility.
Known dimensions
Compare at least three known product measurements and the overall bounding box against the accepted source and unit system.
Coordinate system
Verify up axis, forward direction, local origins, floor contact, wall contact and placement in every supported scene.
Node contract
Confirm every selectable, moving, replaceable, measurable and hideable part uses the identifiers in the approved manifest.
Material reference
Compare representative finishes under approved neutral and scene lighting; verify color space, roughness, metallic and normal behavior.
Option trace
For each visual behavior type, apply a configuration choice and reconcile the state with price, quote, BOM and saved configuration identifiers.
Invalid combinations
Attempt incompatible dimensions, accessories and modules through both UI and direct state input; the scene must not create an unsupported product.
Motion and clearance
Exercise every pivot, transform and animation at boundary states; check clipping, direction, travel and implied physical behavior.
Largest valid scene
Load and interact with the largest accepted product on representative devices and networks; record transfer, parse, memory and render results.
Repeated changes
Change finishes, modules and dimensions repeatedly; verify resources are reused or disposed, memory remains stable and stale parts do not persist.
Export validation
Run the accepted glTF validator and asset audit, review warnings and verify every required extension is supported by each runtime.
Saved revision
Open configurations created against the current and supported earlier asset revisions; verify mappings, appearance, values and document snapshots.
Fallback behavior
Interrupt one asset or decoder dependency and test loading, retry, error messaging, poster or non-3D continuation according to the accepted journey.
Twenty questions for your 3D supplier.
Ask for decisions, owners and evidence. Define what web optimization and format support must achieve in your actual product workflow.
Which files are authoritative for geometry, dimensions, materials and product identity?
Who owns source assets, optimized derivatives, textures, scripts and export profiles?
How are units, axes, origins, scale and floor or wall contact defined?
Which geometry is required for the customer decision, and which stays in CAD or production systems?
How are configurable parts, material slots, pivots and animations named with stable IDs?
Which changes use materials, visibility, transforms, replacement, instancing or procedural geometry?
How does the visual state map to options, price, quote, BOM and production identifiers?
Which glTF extensions does each target viewer actually support?
How are geometry and texture compression selected and measured?
What are the representative products, devices, browsers, networks and largest valid scenes?
Which transfer, decode, memory, render and first-interaction measures are acceptance criteria?
How are PBR materials approved against physical or brand references?
How are transparency, glass, fabrics, wood, metallic coatings, emission and normal detail tested?
What validator, asset auditor and automated pipeline checks run before publishing?
How are asset revisions, compatible product-data revisions, hashes and rollbacks recorded?
What happens to saved projects and quotes when a node, material or module changes?
Who approves visual accuracy, behavior, performance and product-data traceability?
What evidence is delivered for acceptance and retained after launch?
How are new products, finishes and modules added without rebuilding every combination?
What happens when a model, texture, decoder or asset service cannot load?
3D asset pipeline questions
Primary technical references
These publishers define the formats, extensions and implementation tools. Your catalogue, behavior and supported customer journey determine hierarchy, budgets and acceptance criteria.
Khronos glTF 2.0 specification
The official specification for the API-neutral runtime asset delivery format, including scenes, nodes, meshes, materials, textures and animations.
Khronos glTF resources
Official overview, validator, asset auditor, PBR, KTX, optimization and real-time asset creation resources.
Khronos 3D Commerce
Industry guidance, tools and resources for creating and presenting scalable 3D product assets across consumer platforms.
Khronos KTX
The portable GPU texture container and ecosystem for efficient texture distribution and transcoding.
Google Draco
The official open-source library for compressing and decompressing 3D geometric meshes and point clouds.
Three.js GLTFLoader
Official runtime loader documentation, including supported glTF extensions and optional Draco, KTX2 and meshopt integration.
Custom software for manufacturers
A configurator up front. Your business connected behind it.
We specialize in complex, configurable and made-to-order products. We build custom software around your catalogue, calculations, permissions, sales process and factory workflows.
Custom software around your product assets
Configurix specializes in complex products. We build custom configurators and business software around your catalogue, rules and sales or factory processes. Scope the visual assets alongside CRM and qualification, calendars and appointments, pricing and quotes, materials and bills of materials, jobs, orders, invoicing and website or system integrations. Product ownership, engineering approval, supported devices and each downstream output are defined for your implementation.
CRM and qualified leads
Capture the selected product, dimensions and options with each enquiry. Qualify by product fit, project requirements and commercial readiness, then assign the next action to the right salesperson.
New enquiry
CAD, glTF and GLB product assets
Product fitQualified
CAD, glTF and GLB product assets
RequirementsProposal
CAD, glTF and GLB product assets
Next actionCalendars and appointments
Let a configured project continue into a sales consultation, technical review, survey or installation appointment. Connect calendars, responsibilities and reminders to the same customer record.
- 09:00Project review
- 11:30Technical review
- 14:00Production planning
Bill of materials and factory data
Map product selections to component codes, quantities, materials and cut lengths. Build the sales or manufacturing BOM your team needs, with revisions and production review rules defined for your products.
| Component | Quantity |
|---|---|
| FRM-01Configured components | 1 |
| PNL-02Materials and quantities | 1 |
| KIT-03Agreed operations | 1 |
Mapped to your product codes
Live prices and branded quotes
Apply your own formulas, price lists, dealer margins and approval rules. Generate a quote containing the saved specification, product images, commercial terms and a clear customer approval step.
Quote revision
Orders, jobs and production
Carry accepted choices into order lines and assigned jobs. Keep product revisions, required approvals, documents and delivery tasks together so sales and the factory work from the same specification.
- Accepted quote01
- Configured order02
- Production job03
- Installation04
Invoicing and accounting
Connect accepted orders to deposits, invoice drafts, payment terms and your accounting workflow. Agree which system issues the invoice and how references and confirmed payment status return to the project.
CAD, glTF and GLB product assets
Built for your website. Connected to your systems.
Launch a branded configurator in your existing website or a custom sales portal. Connect CRM, ERP, PIM, ecommerce, calendars and accounting through available APIs, webhooks or agreed imports. We define the data, permissions and responsibilities for each connection with your team.
- 01Your website
- 02Configurator
- 03CRM & calendar
- 04ERP & accounting
Choose the workflows your implementation needs. We build and validate them against your products, documents and target systems.
Discuss your product assetsMap one real product from source to customer-ready 3D.
Bring the source files, product rules, finish references and the systems you need to connect. We can define the configurator, operational workflow and acceptance evidence around your products.
Connect 3D assets to the rest of the implementation.
3D product customization software
Bind customer text, artwork, colours and approved uploads to stable zones, design revisions and scoped output files.
CAD product configurator
Connect browser-ready 3D and governed configuration state to scoped drawings, CAD automation and released output contracts.
AR product configurator
Prepare scale, origin, materials, formats and configuration identity for accepted WebXR, Scene Viewer and AR Quick Look paths.
3D product visualization software
Connect optimized assets to governed choices, accessible controls, visible state, saved revisions and commercial action.
Product configurator data model
Give every product, option, component, material and revision a stable identity before binding it to 3D.
Implementation guide
Coordinate asset work with catalogue, rules, pricing, outputs, acceptance, launch and maintenance.
Requirements checklist
Write measurable requirements for model sources, materials, performance, behavior and ownership.
Configurator for websites
Plan indexable content, staged 3D loading, mobile interaction, lead capture and analytics.
Maintenance and governance
Control model revisions, product compatibility, publishing, rollback and permanent regression evidence.
3D configurator examples
See which dimensions, modules, finishes and behaviors matter across different product categories.
Configurator testing and QA
Connect asset validation to product rules, prices, outputs, accessibility, performance and release evidence.
3D configurator performance
Measure asset delivery, decoding, first useful product view, interaction, GPU cost and long-session stability end to end.