flux.2, for Fixing the Picture Before It Becomes Geometry
The mesh is only ever as good as the picture it was built from. flux.2 is the step that fixes the picture — a different angle, a cleaner background, another material — before you commit it to the 3D engine.
What flux.2 actually does
It is an image model that takes a picture plus an instruction and returns a revised picture. On this site it is optional and it sits in exactly one place: between the concept image and the 3D engine.
That position is the point. When a generated mesh disappoints, the cause is almost always the reference image — the object was cut off, the angle hid half the form, the background competed with the subject. Editing the picture is far cheaper than hoping a different prompt lands better.
It builds no geometry and touches no mesh. If you are here to understand where the 3D actually comes from, the page you want is the mesh engine — this one is about the twenty seconds before it runs.
flux.2 at a glance
What the step does here, and what it deliberately does not.
| Developer | Black Forest Labs, released as the flux.2 family |
|---|---|
| Task | Image editing — a picture plus an instruction in, a revised picture out |
| Input here | The concept image, plus what you want changed |
| Output | A revised concept image, which you approve before meshing |
| Typical time | Varies with the edit; slower than drawing a fresh concept |
| Role in the pipeline | Optional stage between the concept image and the mesh engine |
| Price here | $0 — no account, no credits, no watermark |
| Commercial use | The edited image and the mesh built from it are yours to ship |
This stage is optional. Skipping it is the common path, and nothing about the pipeline requires you to use it.
Why flux.2 is worth a detour
The edit is optional, but it is the highest-leverage twenty seconds in the whole pipeline.
The picture decides the mesh
Angle, framing and background matter more to the finished geometry than any wording you could add to a prompt.
Targeted, not random
Regenerating rolls the dice on everything. An edit changes the one thing you asked about and leaves the rest of the composition alone.
Cheaper than a bad mesh
The mesh stage is the slow one. Spending a moment on the reference beats waiting a minute for geometry built from a flawed picture.
Still nothing to pay
Like every other step here, it costs nothing and needs no account. There is no credit meter counting your edits.
From your prompt to a finished file
Four stages. The middle two are the only ones that touch a GPU, and you approve the hand-over between them.
Text to 3D or image to 3D
Type a sentence, or drop a photo. Image to 3D skips straight to the mesh stage; text to 3D needs a picture first.
Concept image
z-image-turbo draws your prompt in about six seconds. You keep it, redraw it, or edit it with flux.2.
Mesh and texture
Hunyuan3D-2 turns that one image into geometry and bakes the texture onto it. This is the slow step, and the progress you see is real job state rather than an animation.
Download the .glb
Take the file. Convert it to STL, OBJ or USDZ in your browser if the next tool needs something else.
What flux.2 is good at, and what it is not
Treat it as a retoucher for the reference image, not as a second 3D engine.
Good at
- Changing the angle. Turning the subject to show the form the mesh needs is the most useful edit there is.
- Cleaning the background. Flattening a busy ground to plain colour measurably improves what the 3D engine returns.
- Swapping the material. Wood to metal, matte to glazed — surface changes come through clearly.
- Fixing framing. Bringing a cropped object fully into frame prevents the mesh stage inventing the missing part.
Not good at
- Building geometry. It edits pictures. The mesh comes from Hunyuan3D-2 and only from there.
- Compound instructions. Three changes in one sentence usually gets you one of them and a surprise.
- Preserving fine detail exactly. An edit redraws the image; small details can shift even where you did not ask.
- Being the fast path. Drawing a fresh concept is quicker. Edit when a specific thing is wrong, not out of habit.
Ask for one change at a time. Rotate the object, or clear the background, or change the material — a single clear instruction lands far more reliably than three stacked into one sentence.
The three models we run
That is the complete list. There is no fourth model behind the button and no vendor being resold.
Hunyuan3D-2
The mesh engine. Turns one image into a textured 3D model and bakes the texture on.
Read the specz-image-turbo
Draws the concept image from your text prompt in about six seconds, so text to 3D has something to build from.
Read the specflux.2
Optional concept edits — change the pose, the angle or the material before you commit the picture to the 3D engine.
You are hereMake a 3D model right here
You do not have to go back to the home page. Type a prompt or drop an image, and take the .glb — free, anonymous, no watermark.
flux.2 — frequently asked questions
Optional edits to the concept image before it becomes geometry. It takes the picture plus an instruction and returns a revised picture — a different angle, a plainer background, another material.
Edit when one specific thing is wrong and the rest of the picture is right. Regenerate when the whole composition missed — at six seconds a fresh concept is quicker than talking an edit into shape.
Ask for one change, in plain words, and name the thing you want changed. Rotate the object to a three-quarter view. Make the background plain white. Stacked instructions are where edits usually go wrong.
A little, and it is optional for exactly that reason. It is still far cheaper than running the mesh stage on a reference image you already know is flawed.
Usually, when the edit fixes framing, angle or background. Those three are the most common reasons a generated mesh disappoints, and none of them can be fixed after the geometry exists.
Yes. The edited image and any mesh built from it are yours to ship, with no watermark and no rights claimed by us. Check that whatever you supplied as input was yours to use.
Want to see the output before you commit?
Generate one, then open the .glb in the free viewer and read the triangle count yourself.
Fix the picture, then build the mesh
Draw a concept, edit what is wrong with it, and only then spend the slow minute. Free, anonymous, no watermark.
FreeNo signupNo watermarkDownloads as .glb