RendHQ sits between your source design tool and your destination rendering or coordination platform. You bring the file. RendHQ handles the translation — preserving every material, layer, metadata attribute, and spatial relationship in the process.
Step 01
Add your 3D object
Step 02
Upload source files
Step 03
Download outputs
Step 01
Define your object — name, category, materials, and rendering intent
Every object in RendHQ starts with a structured data entry that becomes the metadata backbone for every file it generates. Standard name, category, model ID, material types and finishes — entered once, embedded in every export format automatically.
Standard name, category (Barn Door Tracks, Doors, Glass Clamps, etc.), and model/series ID — applied consistently across every file format.
Brushed, Chrome, Black, Brushed Modern Brass, Oil Rubbed Bronze, Polished Brass, Polished Gold — selected at object creation, embedded in every downstream export.
Mark whether the object requires rendering outputs. RendHQ generates the appropriate file set for each requested render environment.
Data captured at this step
Step 02
Upload the native files from your design platform — drawings, models, textures
Upload the files your team already has — DWG, DXF, STP, RFA, 3DM, and more. RendHQ reads the source geometry, material assignments, and structural data from your native format without requiring you to export to an intermediate format first.
Upload STP, DWG, RFA, 3DM, BLEND, MAX files directly. RendHQ reads the source without an intermediate conversion step.
Product images attach to the object record and travel with every file export — vendors and visualization teams receive the visual reference alongside the geometry.
STP, DWG, RFA, IGS, 3DM files all live in the same object record. Your team downloads the format they need — no re-requesting, no format conversion.
File types shown in this step
Step 03
One credit. One file type.
Add formats only when you need them.
Each credit you spend converts your source file into one output file type. RendHQ has 15 formats in the library. You choose which format you need for each conversion — and only spend credits on what you actually use. Additional formats are add-ons, keeping your credit balance from being consumed by outputs you never requested.
Spend one credit to convert your source file into one output format — .udatasmith, .fbx, .obj, .usdz, .dwg, or any of the 15 available. You choose which one you need.
Need the same file in three formats? Add them individually. RendOne: +$25/format. RendSupply: $350 unlocks all. RendVision/RendET: all formats included, additional outputs use credits.
.udatasmith + assets ZIP — full scene fidelity including materials, lighting, and object metadata. Ready for direct Twinmotion or Unreal Engine import.
COL, NRM, and METALNESS maps at 4K included alongside every geometry output — no separate texture request, no manual re-linking.
15 formats in library — you choose per conversion
Additional format cost by plan
See full pricing at our pricing page
No switching tools. No pre-conversion. RendHQ reads your native files and outputs to every major rendering and coordination platform.
Source platforms — bring your files from
Rendering destinations — export ready for
Universal exchange
Twinmotion uses Datasmith (.udatasmith) for full scene fidelity — materials, lighting, and object metadata all intact. Universal exchange formats work as both import and export across all platforms.
Do I need to convert my files before uploading?
No. Upload your native files directly — DWG, RFA, STP, 3DM, BLEND, MAX. RendHQ reads source formats without an intermediate conversion step.
What happens to my material specifications on export?
Material assignments, finish codes, and texture references are embedded in every export format. They don't get substituted for defaults during translation.
Can multiple team members access the same object library?
Yes. Object records are shared across your team. Everyone downloads the format they need from the same source — no re-requesting, no separate file management.
How does RendHQ handle objects with multiple finishes?
Each finish defined on an object gets its own complete output file set — Datasmith package, .usdz, .fbx, .obj, MTL, and 4K texture files. All from the same upload.
What rendering platforms does the Datasmith output work with?
Twinmotion and Unreal Engine natively. The .udatasmith file carries full material, lighting, and object metadata for direct import with no re-mapping required.
How long does it take to get files out?
Once uploaded, drawing files are available for download immediately. Rendered outputs are generated per finish and available as soon as processing completes — typically minutes.
Bring your stack. We will walk you through the exact workflow for your platform and file types — live, no setup required.