Sculpting and finishing are different jobs, and there's no rule saying one app has to do both. This is the handoff: how to get a sculpt out of a browser tab and into Blender with its size, its orientation, and its detail intact — and which five things to check the moment it lands. Disclosure up front: Re:Form is our browser sculpting tool and supplies the export side of the examples. Blender is free software made by people who owe us nothing, and it is far more mature than we are; the Blender facts below were checked against Blender's own documentation in August 2026.
Can you take a browser sculpt into Blender?
Yes. Re:Form exports OBJ on every plan and adds STL, GLB, and FBX on Pro, and Blender imports all four with built-in importers — no add-on hunting. Re:Form's world is Z-up to match Blender's convention, and exports are converted so the mesh lands upright. Blender 5.2, released July 14, 2026, is free under the GPL.
That's the short version. The rest of this post is about the parts that go wrong: scale, triangle budgets, smooth shading, and the color data that quietly doesn't survive the trip.
Why hand a sculpt off at all?
Because sculpting and production are separate problems. A sculpting app is built around one thing — pushing a dense surface around at speed — and Re:Form is deliberately narrow in that way. Blender is an entire pipeline: modeling, UVs, rigging, animation, simulation, compositing, and Cycles and EEVEE for rendering. If your sculpt needs to be lit, animated, textured with real image maps, or dropped into a scene with other objects, that work happens downstream.
The trade also runs the other way. Blender's sculpt mode is capable and free, and if you want one program for everything it's the obvious answer — we say so at length in our Blender comparison. What a browser sculptor offers is a start-in-ten-seconds front end on a machine that may not want a 1 GB install, plus the option to sculpt somewhere Blender isn't installed at all. Using both is not a compromise; for a lot of people it's just the workflow.
Which format should you export for Blender?
Export GLB if your sculpt is painted, and OBJ if it isn't. GLB is a single self-contained binary that carries vertex colors as the standard COLOR_0 attribute, which Re:Form writes on export. OBJ carries geometry and UVs in a plain-text file that every tool on earth reads. Both need Blender's stock importers and nothing else. GLB requires Re:Form Pro; OBJ is on the Free plan.
Here's the whole decision in one table:
| You're sending Blender… | Export | Why |
|---|---|---|
| Plain geometry, no color | OBJ | Free plan, universally readable, keeps UVs |
| A vertex-painted sculpt | GLB | Carries COLOR_0 vertex colors in one file |
| A print-bound mesh you'll check in Blender | STL | Triangles only — matches what the slicer wants |
| Something a studio pipeline demands | FBX | Only when a receiving tool asks for it by name |
STL and FBX are on the list for completeness, not because they're good choices here. STL is triangles and nothing else — no UVs, no color, no units — so it's the right call only when the Blender stop is a detour on the way to a printer. FBX is a proprietary interchange format whose main virtue is that other people's pipelines demand it. For a sculpt going into Blender, OBJ and GLB cover almost every case. The format breakdown goes through exactly what each one carries and drops.
What actually gets lost in the export
Every interchange format is lossy, and it's better to know which loss you're accepting.
Sculpt layers do not survive. None of the four formats has a concept of layers. Your sculpt arrives in Blender as one baked surface — the layer stack exists only in Re:Form's native .clay file. Keep the .clay as the master and treat exports as one-way handoffs. If you need to go back and turn a layer down, you go back to the .clay, not to the OBJ.
Roughness and metalness don't ride along on vertex colors. glTF has a legal per-vertex slot for color and no equivalent for per-vertex roughness or metalness, so Re:Form's GLB export carries the color and tells you at export time that the other two channels stay behind in the .clay. That's a format limitation, not a missing feature. You set roughness and metalness in Blender's material instead, which is where you'd want them for rendering anyway.
Quads, if you had them, may become triangles. Sculpted surfaces are dense triangle soup by nature. This matters for edge-loop editing and animation deformation, and barely at all for a still render.
Set the scale before you export, not after
Re:Form has a real-world millimeters-per-unit mapping that scales OBJ, STL, GLB, and FBX exports on the way out. Set it while you're still sculpting and your 32mm mini leaves the app as a 32mm object instead of an arbitrary blob you'll be eyeballing later. This is the single highest-value habit in the whole handoff, and it costs nothing.
Then, in Blender, check what arrived: select the object, open the sidebar in the 3D viewport (N), and read the Dimensions under the Item tab. Blender's scene unit is meters by default, so a millimeter-scale object is legitimately a small number there — 0.032 m for a 32mm mini is correct, not a bug. What you're looking for is an order-of-magnitude surprise: a 1000× or 25.4× error means unit assumptions disagreed somewhere.
If it does land wrong, don't scale it by hand and hope. Blender's OBJ importer has a Scale field and a Clamp Bounding Box option in the import dialog, per the Blender manual as of August 2026, and re-importing with the right number is faster and more repeatable than fixing it in the viewport. The classic 25.4× error is inches-versus-millimeters, and it bites STL hardest because the STL format contains no unit declaration at all.
If it arrives lying on its face
It shouldn't. Blender's native axes are Y forward, Z up. Re:Form's world is also Z-up — that change landed in the 0.6 series specifically to match Blender's convention — and interchange exports are rotated on the way out so models land upright in Blender and in slicers, then rotated back on import. Leave Blender's import axis settings alone and the sculpt should stand up correctly.
If you're importing something else entirely and it does arrive face-down or on its side, the fix is the Forward Axis and Up Axis dropdowns in Blender's import dialog. The manual is explicit about why they exist: many applications use Y as the up axis, and mapping the axes at import time converts between conventions. Rotating the object afterward looks the same in the viewport but leaves the object's rotation values dirty, which comes back to bite you when you parent, rig, or export it again.
The five-minute arrival checklist
Do these in order the moment the mesh appears in Blender. It's the difference between a sculpt that's ready to light and one that renders like a lump of faceted plastic.
- Check Dimensions in the
Nsidebar, as above. Fix scale at the import dialog, not by hand. - Set the origin. An imported sculpt often has its origin at the world center rather than in the object. Object → Set Origin → Origin to Geometry gives you a sane pivot for everything that follows.
- Shade it smooth. Right-click → Shade Smooth, or Shade Auto Smooth, which applies the Smooth by Angle modifier — the current mechanism in Blender's modifier list as of August 2026. Without this, a high-poly sculpt renders as visible facets and everyone assumes the sculpt is bad when the shading is.
- Decide on triangle count. A multi-million-triangle sculpt is fine to render and miserable to interact with. If the viewport crawls, add a Decimate modifier and pull the ratio down until it's comfortable — the modifier is non-destructive, so you can dial it back for the final render.
- Wire up color, if you sent any. A GLB's vertex colors arrive as a color attribute on the mesh. If the model shows up gray in Material Preview, add a Color Attribute node in the shader editor and plug it into the Principled BSDF's Base Color. The data is there; the material just may not be pointed at it.
Do you need to retopologize before importing?
Usually not. Retopology matters when a mesh has to deform — rigged characters, facial animation, game assets with a polygon budget. For a still render, a 3D print, or a turntable of a bust, the dense sculpted mesh Re:Form exports is fine as-is, and Blender's Decimate modifier handles viewport performance without you rebuilding anything by hand.
The honest exception is animation. If your sculpt is going to be rigged and moved, it needs clean quad topology built around the joints, and no automatic tool fully replaces doing that deliberately — Blender has the retopology tooling for it and Re:Form does not. Our retopology vs remeshing explainer covers which one your project actually needs, since the two words get used interchangeably and mean different things.
Going the other way
The trip is not one-directional. Re:Form imports OBJ on every plan and adds STL, GLB, and FBX on Pro, so a base mesh built in Blender — a blocked-out body, a scanned head, a kitbashed prop — can come into the browser to be sculpted on and go back out. Imports are converted back through the same axis handling as exports.
What doesn't round-trip is history. Send a sculpt to Blender, edit the geometry there, bring it back, and you have a new mesh, not your old session with new edits: the layers, the mask, and the undo stack are properties of the .clay file you left behind. Plan the trip so each app owns a phase — sculpt, then finish — rather than bouncing the same object back and forth and wondering where your layer stack went.
What this costs
Blender is free and open source under the GPL, with no tier above it. Re:Form's Free plan covers the whole OBJ path both directions — every brush, sculpt layers, masking, symmetry, remeshing, up to roughly 12.5 million triangles, local .clay saves, no watermark, no card — licensed for personal, non-commercial use. Re:Form Pro is $9.99/month or $99/year and adds the STL, GLB, and FBX formats, the full 50-million-triangle budget, and a commercial license.
So the free version of this workflow is real and complete: sculpt in a browser tab, export OBJ, import to Blender, render in Cycles, and pay nobody. The paid line is specifically GLB — which is what you want if your sculpt is painted — and the right to sell the result. Re:Form is v0.6.7 Alpha, needs a free sign-in, and runs in desktop Chrome, Edge, Firefox, or Safari 26 on WebGPU; phones and tablets aren't supported. You can start sculpting in a tab and have something worth exporting inside an hour, and the FAQ covers the rest of the plan details.
FAQ
Will Blender open a .clay file?
No. .clay is Re:Form's native session format — it snapshots sculpt layers, masks, reference images, and unit settings — and nothing outside Re:Form reads it. To get a sculpt into Blender you export an interchange format: OBJ on any plan, or STL, GLB, and FBX on Pro. Keep the .clay as your master file and treat every export as a copy.
Why is my imported sculpt faceted instead of smooth?
Because Blender imports meshes with flat shading by default, so every triangle catches light as its own plane. Right-click the object and choose Shade Smooth, or Shade Auto Smooth to apply the Smooth by Angle modifier, which keeps hard edges hard while smoothing the rest. This is a shading setting, not a geometry problem — your sculpt is fine, the renderer just hasn't been told to interpolate normals.
Can I sculpt in the browser and render in Blender commercially?
Blender's GPL license places no restriction on what you make with it. Re:Form's Free plan, though, is licensed for personal, non-commercial use only, so selling a render, a print, or a game asset that started as a Free-plan sculpt requires Pro's commercial license at $9.99/month or $99/year. Pro also adds GLB export, which is the format you'd want for a painted sculpt anyway.