3dSynth vs a slicer
A slicer turns a solid mesh into printer moves: perimeters, infill, supports, and a plate of objects. 3dSynth is a generative toolpath and mesh workspace. Some modules write G-code themselves. Others export STL so a slicer can finish the job.
The problem this answers
You searched whether 3dSynth replaces PrusaSlicer, OrcaSlicer, Cura, or Bambu Studio, or when you should still slice. The short answer: it does not replace a general STL slicer. It can skip the slicer for paths it authors, and it can feed a slicer when you need one.
How people do it without 3dSynth
Model or download an STL, slice it, send G-code to the printer. That path owns multi-object plates, tree supports, conventional infill, and vendor-specific presets. FullControl and similar libraries write G-code from code when the path is the design.
How 3dSynth does it
G-code Sculptor, SynthBlocks, Node Sculptor, Fabric Sculpt, Hex Grid, and Custom G-code can produce or edit G-code without sending that path through another slicer. Mesh Sculptor and Texturize export STL for PrusaSlicer, OrcaSlicer, Cura, Bambu Studio, and the rest. Shared printer, material, and nozzle profiles still apply. See FAQ and export STL for slicing.
Example
A spiral lamp: design the wall in G-code Sculptor, preview, export G-code, print. A textured box you still want tree supports on: Mesh Sculptor or Texturize → STL → your usual slicer.
When it works
Vase, spiral, fabric, hex, and other paths where geometry and the nozzle route are the same idea. Learning toolpaths in the browser without an account.
When another tool is better
Use your slicer for supports, multi-part plates, variable line width from a mesh, and anything your printer vendor’s software already owns. 3dSynth is not a drop-in Bambu/Prusa/Orca replacement and is not affiliated with those vendors.
Related: direct G-code · 3dSynth vs CAD · all guides