Which FDM printers work with 3dSynth?
3dSynth ships hundreds of built-in FDM machine profiles. Output is standard G-code plus that profile’s start and end scripts. Brand names in the profile library mean compatible G-code, not an official partnership with Prusa, Bambu Lab, Creality, or anyone else.
The problem this answers
You want to know if your printer will run 3dSynth output. The honest answer: if it already runs ordinary Marlin, Klipper, or similar G-code from a slicer, it can usually run 3dSynth G-code after you pick a matching profile and verify the file. We do not warrant every machine.
How people do it without 3dSynth
Vendor slicers (Bambu Studio, PrusaSlicer, OrcaSlicer, Cura) own machine presets, filament tables, and sometimes cloud send. You still confirm first-layer and kinematics on hardware you own.
How 3dSynth does it
Print setup is shared across modules: printer, material, nozzle, and process dialect. Docs: printer settings. Clay and plotter dialects exist when the job is not filament. You are responsible for checking travel, extrusion, and bed origin on your hardware. Preview in the app is not a substitute for a dry run on a new machine.
Example
Pick a profile close to your machine, generate a small vase in G-code Sculptor, inspect start G-code, print a short test. If the dialect is wrong, change process settings rather than assuming an OEM blessing.
When it works
Cartesian and typical FDM beds that already accept G-code files. Desktop and browser app share the same profile idea.
When another tool is better
If your vendor requires a closed pipeline (proprietary skip-the-file workflows, AMS-only presets, or a format 3dSynth does not emit), use that vendor’s slicer. 3dSynth is not an official Prusa, Bambu, or Creality product. See 3dSynth vs a slicer and FAQ.
Related: desktop app · exporting G-code · all guides