Cut floating islands out of sliced G-code
Open the sliced file your printer is about to run. Every island printed in mid-air is found on this device - the file never leaves it - and the short ones that land on the body are cut before they turn into spaghetti.
Open this on a computer
A sliced file is too heavy for a phone’s browser. Open this page on a laptop or desktop.
Drop your sliced file hereOpen your sliced file
A sliced 3MF from Bambu Studio or OrcaSlicer, or a .gcode. It is read on this device and never uploaded.
A few hundred layers take a few seconds.
What you get
Islands in the air Lines with nothing under them on the layer below, and nothing beside them to hold on to.
Where they land How many layers up each one meets the body, if it ever does.
What can go A short stack that lands is cut. Anything taller, wider or never landing is marked for your support brush.
A file you can print The cleaned file keeps every other line, and its checksum is written again.
Nothing to cut here: every floating island in this file needs support in the slicer.
When a print starts with spaghetti
A figurine’s ear tips begin as two small rings with nothing under them. The slicer prints them anyway, they fall, and the nozzle drags them around the plate. On the next layer the same loop meets the head and would have held. This tool finds that layer and cuts it, in three steps:
- Open the sliced file above, or drop it onto the box. It stays on your device.
- Read the rows: each floating island with its layer, its filament and whether it can go. The picture beside it shows what is cut and what stays.
- Press Cut islands and load the saved copy in place of the original. The rest of the file is untouched.
What needs support instead
A stack taller than five layers, wider than fifteen square millimetres of plastic, or one that never lands is a part, not a scrap. It stays in the file and the row says where to paint support in the slicer.
The original file is never changed: the cleaned copy is saved beside it under its own name, ending in -cut.
What the cleaner does
An island in the air
Each layer is read as the beads the nozzle lays. A bead with nothing under it on the layer below, and nothing beside it to bond to, is an island: it has no material to stick to and falls. The first layer rests on the bed and never counts.
Where it lands
Each island is followed upward through the beads that ride on it until one of them also touches the body. That is where it lands, and how many layers it hangs. An island nothing ever lands on is marked, never cut.
What is cut
A stack of at most five layers and fifteen square millimetres of plastic that lands on the body: a scrap the slicer could not help printing. Its beads are removed from the file and the extruder is kept in step, so the layer above becomes a short bridge from the body.
Checked before it is saved
The cut file is read back. If a line now floats that did not before, or a bridge longer than 25 mm is left hanging, that cut is undone and the row says why. A bridge the slicer planned is trusted as the slicer laid it.
Beads that hold each other
A bead beside a held bead is held too: that is how every overhang wall prints. Two beads are one piece where they run side by side for longer than a line width, read from the widths the slicer wrote; a touch at a point does not join them.
What it does not do
It does not add supports, change speeds or temperatures, or touch any line it did not cut. What needs support is said with the point to paint; the slicer still has the last word, and the file should be previewed there before it prints.
Questions people ask
Is my file uploaded?
No. The page loads the cleaner into your browser, and the file is read, cleaned and saved on your own device. Nothing about it is sent to us or to anybody else - once the page has loaded, it works with the network switched off.
Which files does it open?
A sliced project from Bambu Studio or OrcaSlicer (.gcode.3mf), and a plain .gcode from them or from PrusaSlicer. A model that has not been sliced yet has no layers to read: slice it first. One sliced plate per file, any number of models on it, up to 300 MB of G-code.
Will my printer accept the cleaned file?
Yes. A sliced 3MF is saved with every other entry byte for byte as it was and the checksum Bambu printers verify written again for the new G-code. A .gcode is saved as text with only the cut lines missing.
Why was an island not cut?
Because it is a part, not a scrap: taller than five layers, wider than fifteen square millimetres, or nothing above it ever lands. Or because the cut was tried and undone: reading the file back showed a line left floating or a bridge too long. The row says which, and where to paint support in the slicer.
What happens to the layer above a cut?
It is printed as the slicer wrote it, now as a bridge from the body: its ends rest on material and the middle spans the gap. The bridge is checked to be short enough, and one the slicer itself marked as a bridge is trusted at any length.
Is it free?
Yes, with no sign-up and no limit on how many files you clean.
How sure is it?
It reads only the toolpath - not your filament, cooling or speeds - and judges by distances a bead can lean and bridge. A cut it makes can still fail, and an island it keeps may have printed. Preview the cleaned file in your slicer before you print it. The tool is free and provided as is, without any warranty: we are not responsible for prints, material or time lost on a file cleaned here.
Keep every print with its figures
LayerFlow3D reads what the slicer measured - grams, hours, plates - from the same sliced files, and prices every order from them.