Non-G-code data can be embedded in G-code files, like embedded base64 encoded thumbnails. I was wondering, is there is a common way to include (at least the most important) slicer settings that were used to generate that particular G-code file?

I have more and more design files and sliced G-code files, in OctoPrint folders and I sometimes really want to know what settings I used to slice it. For example, after the new Cura 5.5 upgrade, I was constantly wondering, which version I used for each independent file.

Also, I sometimes chose a different quality (layer height) or different infill percentage or scale. I now work around it by using a self-made file naming convention that consists of this:


- v Slicer Version (in my case always Cura)
- n Nozzle size (in mm)
- q Quality (Layer Height without the dot)
- s Scale percentage (0-100)
- i Infill percentage (0-100)
- a Amount (if object is multiplied)

But I really would like to see those things back in OctoPrint when opening a G-code file, so I can decide if I need to reslice, is there a plugin for Cura and OctoPrint, or a standardized way to save this info embedded in a G-code file and show it in OctoPrint?

  • 3
    $\begingroup$ While it is not the G-code file, a .3mf file contains all the slicer parameters and includes the 3D model. Would that fill your needs? $\endgroup$
    – agarza
    Nov 1, 2023 at 0:40
  • $\begingroup$ I never really checked out the 3mf standard. It seems to be very interesting and what I asked for. Thanks for pointing that out. For reference: youtube.com/watch?v=BABdR9d8Cp4. Now I need to figure out and test if both OctoPrint and Marlin/Jyers for Creality Ender 3 v2 supports 3mf instead of stl. Do you know of any such solution particular for STL too? $\endgroup$
    – Bob Ortiz
    Nov 1, 2023 at 8:25
  • $\begingroup$ Most slicers support the 3mf file format. From there, just slice the file as normal then send to your printer. $\endgroup$
    – agarza
    Nov 1, 2023 at 13:22
  • $\begingroup$ Last comment is my mistake "instead of stl" should be "instead of gcode". But this is exactly my problem. If 3mf can't be send to printer/octo, the actual file on the printer, I just have another file to keep track of. I see the value of 3mf for archiving the model with slice settings, but if there is still a separate gcode file for the printer, it defeats the purpose and doesn't solve my issue. Which is why I need to use the naming convention unfortunately. If I send gcode, my printer or octopi won't know the settings I used and I need to search back for my 3mf file to check. $\endgroup$
    – Bob Ortiz
    Nov 1, 2023 at 13:34
  • $\begingroup$ Wouldn't it be easier to track the 3mf files on your computer instead of saving the G-code files? If the G-code file doesn't have the settings you need, you would still have to reload the stl, adjust your settings, slice the file, and then send it to the printer. $\endgroup$
    – agarza
    Nov 1, 2023 at 13:43

1 Answer 1


Cura already stores all the slicer settings in the G-code file as comments. Install a G-code file viewer or file editor plugin in OctoPrint to view the used slicer settings for that specific G-code in OctoPrint.

The GcodeEditor plugin has the ability to view the actual G-code.


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .