Downloaded G-code: checks before running it on a printer
A G-code already contains instructions intended for a printer and configuration. Prusa publishes its sample files by model, alongside STL/3MF geometry and a presliced file; that does not show that a G-code from another source matches your machine. This is a documentary checklist for checking the details available and, when they are missing, starting from geometry with an appropriate profile.
The short answer
Before running a downloaded G-code, check which printer it was prepared for, the hardware settings it identifies, and any firmware version stated for that file. Prusa sample G-codes are described as tested for listed models; some Prusa families show a compatibility warning, but it does not inspect the whole file. If the target model or setup remains unclear, start from the geometry and re-slice it with a profile appropriate to your printer.
Why G-code depends on a printer configuration
A slicer turns a geometric model and selected settings into G-code instructions. The resulting file depends on those preparation choices. To change orientation, supports, or material settings, return to the model and generate a new file with an appropriate profile. A 3MF project may also contain settings: check them during import before slicing again.
The Original Prusa sample page says its archives contain geometry (.stl/.3mf) and a presliced version (.gcode), and describes those examples as tested and tailored for the relevant Prusa printer model. The table lists machines and some variants separately. That is evidence about those Prusa archives, not validation of G-code posted elsewhere or proof that table entries are interchangeable.
For a G-code from a creator or another platform, look for the target printer, declared setup and any version notes. If they are missing, the filename alone cannot establish a match. The files and slicing profiles page may help locate metadata, but the check still applies to the specific file.
First check: the exact model and the firmware version
Record the full model name as shown on the printer or its documentation, then look for that same designation on the page offering the G-code. The Prusa table presents several combinations as separate entries; that layout alone does not prove a file can never work elsewhere, but it also does not claim interchangeability.
The MK4/MK3.9 note in the Prusa archive separates Input Shaper and non-Input-Shaper files and calls for firmware 5.0.0 or newer for the former. That requirement applies to those specific G-codes. Do not transfer the number to other archives or models; find the note for the exact downloaded file.
Record the model, any stated firmware version, and the source page. If the uploader does not provide those details, mark them as unknown; do not infer a file’s target from a printer family or a photograph.
Nozzle, sheet and material: the hardware settings to compare
When generating new G-code from geometry, the PrusaSlicer 3.0 Public Preview guide asks users to check nozzle size and type and the print sheet in the profile, then choose the intended printer and material. These are setup steps for preparing a file. They do not mean a presliced file exposes a complete, verifiable record of every parameter.
The material selected in the slicer is part of the profile context used to generate the file. For downloaded G-code, the actual loaded material and encoded settings may not be described on the source page. Look for that information there; if it is missing, do not assume the creator’s profile suits your filament.
Use a separate checklist: target model, any stated version, nozzle and other explicitly identified hardware, declared material, and archive notes. Mark undocumented fields as unknown. A missing value calls for a provenance check or re-slicing the geometry; do not fill it in by guessing.
The "G-code isn't fully compatible" message on recent Prusa printers
Prusa documents the “The G-code isn't fully compatible” warning for the printer families it lists. It says the printer compares the file with saved hardware settings and points users in particular to the model, nozzle parameters and other settings in the Hardware menu. The article provides different error codes for the listed models.
The page advises comparing the G-code with hardware settings in the LCD menu. Make that comparison when the warning appears; do not dismiss it on the assumption that the file is correct. If you cannot identify the difference or the intended setup, return to the geometry and re-slice using your printer profile.
This warning is a documented check on the listed Prusa machines. The page does not say it inspects every instruction, the material actually loaded or every printing risk. Likewise, no warning is not a certificate of compatibility or safety for an unknown G-code.
Prefer the geometry and re-slice with a matching profile
If you have geometry rather than G-code, the PrusaSlicer 3.0 Public Preview guide documents importing 3MF, STL, OBJ, STEP/STP and SVG. Choose the printer, check its hardware settings in the profile, then select the material and slicing profile for your job. The software generates a new file for the choices you made; it does not validate the original G-code.
A 3MF project may contain more than meshes: the guide says it can hold the whole project and bring its own printer, filament and print settings, potentially replacing yours when opened. After import, check which profile is active and decide whether to keep the project settings or your machine’s settings. Unknown 3MF projects need this provenance check.
The guide places move and orientation tools in Prepare, followed by layer-by-layer inspection in Preview. Use these views to examine the slicing you generated. The cited documentation describes a getting-started workflow; it does not certify that any file or model is ready to print on every machine.
Check in Preview, export, then watch the first layer
In PrusaSlicer 3.0 Public Preview, Preview lets you move through the layers. Compare the displayed shape with the intended model, examine areas that appear to float without support, and check that the first layer matches the planned footprint on the bed. This preview inspection helps identify preparation problems; it neither measures a printed part nor validates every instruction in G-code obtained elsewhere.
The guide says export can produce .gcode or .bgcode; the latter contains the same instructions in compact binary form and is described as smaller and faster for the printer to read. For export to removable media, the page says to use Eject when offered. These are PrusaSlicer workflow details, not proof that every printer reads both formats or that a downloaded file is compatible.
Once the setup is confirmed and the file prepared, the guide recommends watching the first layer at startup. Check adhesion and printer behavior, then use the manufacturer’s stopping procedure if operation is abnormal. An adhering first layer does not guarantee the outcome of the whole part; observing it complements preparation and compatibility checks.
Sources and limits
- Prusa — Sample G-code by printer model
- Prusa — G-code compatibility warning
- Prusa — First print, PrusaSlicer 3.0 Public Preview
We organize manufacturer and community documentation; we have not measured these products ourselves. The manual for your exact model takes precedence over general guidance.
A clearer shortlist starts with your projects.
Use the free buying checklist and budget worksheet before comparing offers.