Keep your file yours.
Choose a text G-code file from your slicer. Parsing runs in a background worker. Your print file is not sent to a server or stored in browser history.
THE CHROMATIC OBSERVATORY
/ 02
Every layer.
In full color.
See every filament change before printing begins. A precise, private workspace for the moments that make your print unique.
◈ Local processing◉ Read-only↳ No sign-up
SPECIMEN / 001ILLUSTRATIVE DEMO
TEALAMBERROSEVIOLET
Drop your G-code. Reveal the spectrum.
Text .gcode / .gco / .gc · up to 150 MB · processed on your device
LOCAL ANALYSIS / No G-code upload. No account needed.
Or paste a short G-code snippet
01 / PRECISION WORKSPACE
Your print, decoded.
DEMO / SYNTHETIC DATA
LAYERS—
CHANGE EVENTS—
PRINTED Z RANGE—
G-CODE LINES—
X / Y • mm
TIP / Focus the preview and use ← → to move one layer. Drag to rotate in 3D.
02 / SWAP REPORT
A sequence you can prepare for.
| EVENT | COMMAND / TYPE | LAYER / Z | LINE | FILE TIME¹ |
|---|
¹ The last elapsed-time checkpoint in the file is shown; it is not an exact event time or live printing schedule.
PREVIEW ≠ PRINT VALIDATION · Colors are assigned by you. Verify commands in your slicer and firmware.Read the field guide ↗
THE WORKFLOW
From machine code to a clear plan.
Find the exact moment.
Select an event to synchronize its layer, source command and spectrum. Scrub the layer slider to inspect linear extrusion paths in 2D or a rotatable 3D stack.
Print with a checklist.
Assign preview colors and export source-line events as CSV. Check the original slicer preview and your printer firmware before starting a print.
FIELD NOTES / SUPPORTED COMMANDS
Read the signal. Know the limits.
M600 · explicit filament-change command
M600 requests a filament-change routine in compatible firmware. Detection confirms the command is present; it does not confirm that the printer supports it, or that a physical color change occurs.
M0 / M1 / M25 / M226 / PAUSE · candidates
Pause commands can be used for inserts, inspection or filament replacement. They are marked as candidates rather than confirmed color changes. Firmware macros and proprietary multi-material sequences may require manual inspection.
Tn · tool selection
The first tool selection establishes the initial tool; subsequent changes are listed. Tool changes can happen several times in a single layer. A tool number is not a verified filament color.
Layer reconstruction & preview accuracy
The parser tracks G0/G1, G90/G91, M82/M83, G92, G20/G21 and per-tool extrusion positions. Layers are reconstructed from the Z height of positive extrusion, so a travel Z-hop does not create a layer. Preview layers use a zero-based index. Nonplanar paths, firmware retraction, volumetric extrusion, macros and G2/G3 arcs are not fully simulated. Arc geometry is omitted and flagged. This is not a printer safety validator or slicer replacement.
Memory is bounded: very dense layers and files use sampled preview paths, disclosed after parsing. Event records stay in command order. Binary .bgcode, archives and 3MF are not accepted.
FREQUENT QUESTIONS
Before your next print.
Does my G-code leave my device?
No. The analyzer reads files locally and creates downloads in your browser. We do not save analysis history. Blogger, Google services and existing advertising may process ordinary page-visit data independently of your G-code.
Why are the colors different from my filament?
This version uses a clearly labeled user-assigned palette. G-code often contains no reliable physical color data. Change the palette swatches to match your spools; this changes the preview only.
Why is the event count different from my swap count?
Pauses, filament commands and tool switches have different meanings. Some are setup commands; some pauses do not involve color; proprietary macros may hide changes. Check the source line and event type. A zero-event file remains a valid result.
Can this modify or send instructions to my printer?
No. This is a read-only planning tool. CSV export is a checklist, not executable G-code. Always verify the original file with your slicer and printer documentation.
What if the file fails to load?
Export plain text G-code, keep the file under 150 MB and try again. Binary G-code must be converted with your slicer. Files with no positive linear extrusion cannot produce a path preview.
Privacy & local processing
Print files remain on your device. No analysis history, cookies or local storage are created by this tool. Existing Blogger and advertising services retain their own policies.
Google Privacy Policy ↗About & feedback
CHROMA TRACE is an independent color-change planning utility for makers. It is not affiliated with printer, slicer or firmware manufacturers. Report unexpected output with the command type and a non-sensitive minimal example.
Publisher profile / contact ↗