G-code Viewer & Print Time Estimator Community
Questions, answers and tips from people who use the G-code Viewer & Print Time Estimator. 3D + 2D G-code preview by feature, speed and layer, with time and flow stats.
Ask a question about G-code Viewer & Print Time Estimator
Anyone can read this page. To ask a question, reply or vote, please log in. It takes under a minute.
Log in to askNo questions yet. Yours can be first.
This page shows only real posts from real people, so it starts empty. The guide below has the questions people most often have about the G-code Viewer & Print Time Estimator. Pick one to start a thread, or write your own.
From the tool guide: common questions about G-code Viewer & Print Time Estimator
The items below are not posts by community members. They come from the written guide for this tool and are here to get a conversation started. Use “Ask a follow-up” to open a thread about any of them.
Does it support arc moves (G2/G3)?
Yes — arcs are approximated by short segments so Klipper/Prusa/Orca arc-fitted files display correctly.
From the tool guide Ask a follow-upWhat about binary G-code (.bgcode)?
Export plain ASCII G-code from your slicer; binary .bgcode is not supported.
From the tool guide Ask a follow-upHow is the time estimate calculated?
From a Marlin-style look-ahead planner using the file's acceleration (or a default you can change in the estimator tool), shown next to the slicer's own estimate.
From the tool guide Ask a follow-upWhat file types are supported?
Plain-text G-code: .gcode, .gco, .nc and .txt exports from common FDM slicers.
From the tool guide Ask a follow-upIs the print time exact?
When the slicer embedded its own time estimate as a comment, that figure is used and is generally close to the real print time. Without one, the time is estimated from real feedrate and distance and tends to run a little faster than the real print.
From the tool guide Ask a follow-upHow is filament length calculated?
From the real cumulative extrusion (E-axis) values across every extruding move, correctly handling both absolute (M82) and relative (M83) extrusion modes.
From the tool guide Ask a follow-upDoes it support resin/SLA G-code or other non-FDM formats?
No — this parses FDM-style G0/G1 motion and E-axis extrusion G-code specifically.
From the tool guide Ask a follow-upIs my file uploaded anywhere?
No. Parsing and rendering happen entirely in your browser; the file is never sent to a server.
From the tool guide Ask a follow-upCan it handle very large G-code files?
Yes, though files with several million lines may take a few seconds to parse before the viewer becomes interactive.
From the tool guide Ask a follow-upWhat this tool does
A sliced .gcode file is the exact set of moves your printer will make. This viewer parses every G0/G1/G2/G3 move in a background thread (so the page stays smooth even on million-line files), detects layers from the slicer's own markers (or from Z moves), recognises feature types written by Cura, PrusaSlicer, OrcaSlicer, Bambu Studio and SuperSlicer, and shows the print in a 3D view you can orbit, with a layer-range slider, an in-layer scrub slider, an animate button and colouring by feature type, speed or height. A 2D layer view and per-layer time and feature charts complete the picture.
How to use it, step by step
- Drop in or choose a .gcode (or .gco / .nc) file.
- Use the layer slider or press Play to step through the real toolpath.
- Read the real filament length, estimated weight and layer count.
- Check the estimated print time and print bounding box.
Tips from the guide
- When a slicer's own embedded time comment is available, it is shown and used as the headline estimate, since it accounts for acceleration and jerk settings that a simple feedrate-and-distance calculation cannot.
- The fallback time estimate (used only when no slicer comment is found) integrates real feedrate against real travel distance per move, so it is a reasonable planning number but will typically run a little faster than a real print, which also spends time accelerating, decelerating and on non-modeled pauses.
- Very large multi-part or vase-mode files can have a very high layer count — use the slider to jump directly to a layer instead of stepping through one by one.
Common mistakes to avoid
- Assuming the fallback time estimate (when no slicer comment exists) will exactly match the real printer clock — it ignores acceleration/jerk and any pauses, so treat it as an approximation.
- Confusing travel moves (non-extruding repositioning) with the actual printed path when reading the toolpath view — only extruding moves represent real deposited material.
- Loading a non-G-code text file and expecting meaningful stats — the parser looks for real G0/G1/G92 motion commands, and a file without them will show empty results.
Who uses it
- Makers double-checking a file before sending it to print. Confirm the real dimensions, filament use and estimated time match what was intended.
- Anyone sharing G-code who wants a quick visual without opening a slicer. Preview the real toolpath and stats directly in the browser.
- People troubleshooting a failed print. Step through the real layer-by-layer path to spot where travel moves or extrusion look wrong.
How to ask a question people can answer
A good thread on the G-code Viewer & Print Time Estimator saves everyone time. Start with a title that names the exact problem, such as the input you used, the result you expected and the result you got. A title like “Not working” is hard to answer, while a title with the specifics gets replies quickly.
- Say what you tried. List the steps you followed and any settings you changed, so replies do not repeat what you already did.
- Share a small example. A short sample input and the output you saw is worth more than a long description. Remove anything private first.
- Mention your setup. Your device, browser and whether you are on a phone or a computer can explain many odd results.
- One question per thread. Separate topics get clearer answers and are easier to find later with the search box above.
- Come back and reply. If a suggestion worked, say so and upvote it, and if you found the fix yourself, post it for the next person.
Community rules
Be kind, stay on topic and keep personal data out of your posts. Do not post adult, hateful or illegal content, advertising or repeated links. Every post is shown with its author’s username and date, and posts that break these rules can be hidden by moderators. This space is for help with the G-code Viewer & Print Time Estimator and related tasks, and it is separate from the sitewide discussion forum where broader topics live.