OrcaSlicer Normal vs Tree Supports: When To Use Each (2026)

I scrap-binned a Spider-Man bust last winter because Normal supports left a scar pattern across the back of his head that no amount of sanding fixed. I switched to Organic, reprinted the same STL, and pulled the supports off in three minutes flat with my fingernails.

Different jobs want different supports. OrcaSlicer’s six options aren’t equal, and one of them is documented broken in 2026. This guide is the decision tree, not the deep dive. If you want the full breakdown of how branches grow, see our tree supports deep dive; if you want the wider settings landscape, this article is part of our OrcaSlicer settings master guide.

I’m writing this for the intermediate user who has tried both families, gotten burned at least once, and wants to stop guessing. Here’s the short version: Organic is the right default about 80% of the time. Normal still wins on flat overhangs, time-critical jobs, and soluble support workflows. Tree Hybrid is the worst-of-both-worlds in 2026; skip it. Now let me prove all of that.

Table of contents

• The TL;DR decision matrix
• Two families, six implementations
• How we got here (Cura, Rahm, PrusaSlicer, Orca)
• When to pick Normal (Grid or Snug)
• When to pick Organic
• When to pick Tree Slim or Strong
• Why to skip Tree Hybrid in 2026
• Settings that matter regardless of style
• Material and time, honest numbers
• Common pain points and fixes
• When style choice doesn’t matter
• FAQ
• Cheat sheet

The TL;DR decision matrix

If you only read one block in this article, read this one. I built the table from a year of my own prints plus the recommendations in Discussion #10609 on the OrcaSlicer repo, where users have been ranking these styles against each other for over a year.

The single rule under the matrix: pick Organic by default. Switch to Normal Grid for flat mechanical overhangs and soluble workflows. Reach for Tree Slim or Strong only when adaptive layer height is on or Organic struggles. Don’t touch Hybrid yet.

Two families, six implementations

Most write-ups call this a three-style choice. That’s wrong. OrcaSlicer’s Style dropdown exposes six values, but they fall into two families. I’ll break them down so the menu stops looking arbitrary.

Normal family (vertical pillars)

Grid is the default for Normal. Pillars project on a regular XY grid that ignores the overhang outline, so the supports may extend beyond the model footprint. The wiki literally says “projecting the supports into a regular grid will create more stable supports.” It slices fast, it’s the most predictable to reason about, and it’s the heaviest material user of all six styles. It also leaves the worst contact-face scarring because the regular grid pattern imprints across the entire overhang.

Snug is Grid with one rule changed: the tower outline matches the overhang outline and never extends past it. The wiki tooltip is honest about the trade-off: “Snug support towers will save material and reduce object scarring.” You get a smaller footprint and slightly cleaner edges, but tall thin towers wobble more, and the contact face still has a regular grid pattern, just contained.

Tree family (angled branches)

Organic is the current OrcaSlicer default for Tree. The wiki describes it as “default style for tree support, which merges slim and organic style branches more aggressively and saves material.” Smooth curved branches knot-merge near the base, contact tips are precise, and the algorithm uses the least material of any style on most figurines.

Tree Slim uses thinner branches and less aggressive knot-merging than Organic. The wiki: “Slim tree support branches are designed to be more delicate and use less material while still providing adequate support.” Slim is the community pick when you’ve enabled adaptive layer height, because Organic and adaptive LH don’t get along (more on that in a minute).

Tree Strong uses thicker branches and a lower angle than Slim. The wiki: “Strong tree support branches are designed to be more robust and provide additional support for heavier overhangs.” Some long-time users (see Issue #2400) consider Strong the “old default” before Organic took over.

Tree Hybrid tries to mix tree branches for narrow overhangs with normal grid for wide flat overhangs, automatically per region. The wiki text is “Create similar structure to normal support under large flat overhangs.” That’s the intent. Reality: it’s broken. Keep reading for the cautionary section.

Why “Hybrid” sounds great and is actually a trap

I wanted Hybrid to work. The first time I read the tooltip I thought “finally, one style for everything.” Then I printed a thumb plate with a 60mm flat overhang and watched the contact tips snap off mid-bridge. Issue #6618 describes exactly what I saw, and it was closed “not planned.” Discussion #10609 ranks Hybrid last on contact-layer quality of all four tree styles. Issue #10359 documents a separate first-layer base bug in 2.3.1-dev where Hybrid uses the wrong extrusion width on the base layer. Three independent failure modes, no fix on the roadmap. I’ll come back to it lower down, but the short answer is don’t use it.

How we got here

The tree family in OrcaSlicer didn’t appear out of nowhere. Cura had tree supports first. In June 2020 a contributor named Thomas Rahm forked Cura and rewrote the algorithm to be smoother and better at merging branches. UltiMaker shipped Rahm’s work as the “Xmas” alpha (Cura 5.3 Alpha + Xmas), then merged it into Cura 5.4 stable. PrusaSlicer 2.6 picked up the same algorithmic ideas in 2023 and shipped them as “Organic Supports.” OrcaSlicer inherited Organic from there, alongside the older Slim and Strong implementations that pre-date Rahm’s rewrite.

So when I say Organic is a different algorithm, I mean it literally. Slim and Strong are the older tree code with different parameter envelopes. Organic is the newer Rahm-derived algorithm with knot-merging behavior the older code doesn’t have. That’s why Slim slices fast and Organic crawls. That’s why Slim works with adaptive layer height and Organic doesn’t.

When to pick Normal (Grid or Snug)

I reach for Normal in four situations and I want to walk through each one because the reasoning matters more than the rule.

Functional flat overhangs on mechanical parts. Brackets, plates, enclosures. The contact face never gets seen. The overhang is broad and flat, so a tree algorithm will just place a forest of trunks under it that costs the same material as a grid would have, plus more slicing time. Normal Grid is the right call. Snug is fine if you want to save a little material at the edges.

Soluble support workflow. If you’re running PVA or BVOH on an AMS or MMU, you don’t care about contact-face scarring because the soluble interface dissolves cleanly. What you do care about is the curved-branch geometry of Organic playing badly with soluble materials, which often print with poor inter-layer adhesion and snap on the long unsupported branches. Normal Grid with a soluble interface is the proven workflow. There’s a longer write-up in our multi-color print guide and the Bambu AMS guide.

Time-critical prints where slicing speed matters. If you’re iterating on settings, batching a plate of 30 STLs, or running a print farm, Organic will hurt. I’ve seen Organic add 90 seconds of slicing on a part Normal Grid handled in 4 seconds. Issue #9064 documents one user whose model went from 3.8 seconds in Orca 2.2 to 1m48s in 2.3 because of an Organic regression.

Anything that will be sanded, glued, or hidden. Print speed matters more than finish quality if the surface is going to disappear under filler primer or two-part epoxy. Normal Grid is fastest to print, fastest to slice, and the scars don’t matter.

Grid vs Snug. Same family. Grid extends past the model footprint and gives you the most stable tall towers. Snug stays within the overhang outline and wastes a bit less filament. I default to Grid because the stability is worth a few extra grams.

When to pick Organic (the default Tree)

Organic is what I pick first, and I think for most readers that’s the right instinct. The contact tips are tight, the branches knot-merge cleanly so the support pile occupies less volume, and the contact face comes out almost invisible at a 0.20mm Top Z Distance with two interface layers. I’ve removed Organic supports from a printed bust by hand without pliers more times than I can count.

Pick Organic for figurines and busts. Pick it for sculpted character models, dragons, anything with curved surfaces and overhangs at weird angles. Pick it for prints where the support contact face will be visible after removal. Honestly, pick it for most things. The 80% rule is mine, but it’s not arbitrary; it tracks with what people post in Discussion #10609.

Organic has two real trade-offs you should know about before you commit. First, slicing time. Organic is 2x to 3x slower to slice than Normal on typical models, and the regression in 2.3 (Issue #9064) made some models dramatically worse. If you’re iterating on a single STL, fine. If you’re slicing 20 things in a row, you’ll feel it. 16 GB of RAM is the practical recommendation for large Organic models.

Second, adaptive layer height. The setting `tree_support_adaptive_layer_height` exists in the UI but doesn’t work properly with Organic; supports either pass through the model or fall short. Issue #11215 and Issue #10650 are the canonical reports. The workaround is the next section.

When to pick Tree Slim or Strong

Slim and Strong are what I reach for in three specific situations.

Tree Slim with adaptive layer height enabled. Because Organic doesn’t currently work with variable layer height, Slim is the workaround. It’s not as smooth on the contact face as Organic, but the branches still merge nicely and the scarring is much better than Normal. If you’re using adaptive layer height on a sculpted model, Slim is your style.

Tree Slim for fine miniatures. The thinner branches mean Slim can reach into tighter geometry without colliding with model walls. Some miniature painters swear by Slim over Organic for 28mm and 32mm scale. I’ve used both and they’re close, but Slim does win on fiddly geometry where Organic’s chunkier knots get in the way.

Tree Strong when Slim breaks or overhangs are heavy. If you’ve printed a tall narrow model with Slim and the supports cracked between layers, Strong is the answer. Thicker branches, lower angle, more material per support. Issue #8885 documents the pattern of branches snapping on tall prints; Strong fixes most of those cases. Strong is also what I pick on a 0.6mm or 0.8mm nozzle where the chunkier extrusions need chunkier supports.

Issue #6456 covers the historic 0.2mm-nozzle weakness with tree supports; it was closed as not planned, so the underlying complaint hasn’t been formally resolved, but most users report Organic works on 0.2mm now anyway. If you’re still seeing failures, Slim or Strong with a manually bumped branch diameter is the safest fallback.

Why to skip Tree Hybrid in 2026

I want to be plain about this because I’ve burned filament and time on Hybrid more than once and I don’t want you to.

The promise is great. Trees for narrow overhangs, normal grid for wide flat overhangs, both in one object, decided automatically by the slicer. If it worked, it would be the obvious default for mixed-geometry models.

It doesn’t work. Three documented problems, all currently unresolved.

1. Sparse fragile contact tips on flat overhangs. Issue #6618 describes Hybrid producing “lots of tiny support tips that are highly likely to get torn off when bridging.” That issue was closed “not planned,” meaning the maintainers don’t intend to fix it.
2. First-layer base bug. Issue #10359 documents Hybrid using the wrong extrusion width for the first layer of the base interface in 2.3.1-dev. Adhesion suffers.
3. Worst contact quality of the four tree styles. Discussion #10609 aggregates user reports and ranks Hybrid last on contact-face finish across the tree family.

If you have a mixed-geometry model where you genuinely need both, the right move in 2026 is to use Organic everywhere and let the algorithm handle the flat overhangs (it does, just with more material than a grid would), or use Normal Grid everywhere, or use Support Painting to manually mark the regions you want supported. The paint-on workflow is documented in the OrcaSlicer wiki and there are good YouTube walkthroughs. Discussion #8076 tracks the long-running community request for proper per-region style mixing; it’s not shipped yet.

So: skip Hybrid. I’ll revisit if there’s a fix in a future release.

The settings that matter regardless of style

Honest take: people argue about style choice and ignore the four settings that actually drive print quality. Tune these correctly and the gap between styles narrows.

Top Z Distance (`support_top_z_distance`)

The single biggest scarring lever. The vertical gap between the top of your support interface and the underside of the model. Lower means cleaner finish but supports fuse. Higher means easier removal at the cost of rougher overhang surface.

Per-material starting points: PLA 0.20mm, PETG 0.20 to 0.25mm, ABS / ASA 0.15 to 0.20mm, TPU 0.25mm. General rule is 0.5x to 2x layer height. For more, see our filament settings guide.

Bottom Z Distance (`support_bottom_z_distance`)

Same idea for supports that grow on the model surface (not from the build plate). Same range. Matters less because most users avoid model-on-model supports when they can.

Threshold Angle (`support_threshold_angle`)

Default in Orca is 40 degrees. The slicer auto-supports any overhang shallower than this. Lower = more supports (safer); higher = fewer (cleaner, riskier). Per-material starts: PLA on a tuned printer 45 to 55, PETG 50 to 55, ABS / ASA 35 to 40.

Run a calibration pass before pushing threshold angle hard. A temperature tower tells you whether you’re cooling well enough to support a 55-degree PLA overhang without supports.

Interface Layers (`support_interface_top_layers`)

Default is 2. The dense layers against the model. Two is good baseline. Three if rough after removal. Zero if you’re using soluble interface only. Pair with `support_interface_spacing`: 0 = solid, default 0.2 to 0.5mm. Solid plus 2 layers gives smoother overhang but is harder to break off.

Tree-only settings worth knowing

• Tip Diameter (`tree_support_tip_diameter`): ~0.8mm default. Smaller = cleaner contact, less stable.
• Branch Diameter (`tree_support_branch_diameter`): trunk thickness, ~2mm default. Bump for 0.2mm nozzles or large prints where trunks crack.
• Branch Angle (`tree_support_branch_angle`): how far a branch can lean. Higher = more reach, less stable.
• Branch Density (`tree_support_top_rate`): density at contact tips. 80% to 100% for fragile features.
• Branch Distance (`tree_support_branch_distance`): spacing between contact nodes.

The tree supports deep dive walks through each parameter with sliced previews.

The hidden global levers

• Support Pattern (Rectilinear, Grid, Lines, Honeycomb, Lightning, Hollow): only affects Normal supports. Lightning saves time on prototypes.
• Support Critical Regions Only: supports only sharp tails and cantilevers. Has bug history (Issues #2195, #6924); test before trusting.
• On Build Plate Only: supports only grow from the plate. Saves material but blocks supports under deep recesses.
• Support Object Expand Distance: 0.20 to 0.30mm. Pushes supports off model walls horizontally.

Material and time, honest numbers

I want to be careful here because there are wild claims floating around that don’t generalize. Here’s what I trust.

Material savings. Tree styles typically use 20% to 40% less filament than Normal Grid on complex models like figurines. The big “75 to 80% savings” number comes from one Clever Creations sample print on PrusaSlicer Organic vs Grid, and it’s geometry-specific; don’t promise that to anyone. On a flat mechanical part, the savings shrink dramatically because Grid is already efficient at supporting flat shapes. The right framing: Tree wins on complex shapes; the gap closes on simple ones.

Slicing time. Normal Grid is the 1x baseline. Snug is 1.0x to 1.2x. Tree Slim and Strong are roughly 1.5x to 2x. Organic is typically 2x to 3x baseline and can spike higher on dense models. The 2.3 regression in Issue #9064 made some models dramatically worse than that.

Print time. Tree styles usually print faster overall because less material is laid down. The exception is small flat overhangs where Normal is already minimal. Per-layer travel goes up on Organic because of the curved direction changes; on a printer with low acceleration that travel time can eat into the gains.

The honest summary: Organic saves material and print time on complex shapes; Normal saves slicing time everywhere; on simple flat overhangs the difference between any of the styles is probably noise.

Common pain points and how to fix them

The same six failure modes keep appearing in forum threads and on the GitHub issue tracker. Here’s the cheat sheet.

For anything weirder than these, the master OrcaSlicer troubleshooting guide covers the broader print-failure tree.

When style choice doesn’t matter

Honest section. Don’t overthink it in these cases.

• Overhangs steeper than 60 degrees on PLA on a tuned printer: you may not need supports at all. Run an overhang test first.
• Bridges shorter than 5mm: probably prints fine without supports. Tune cooling instead.
• Models you’ll sand or paint: scarring is irrelevant. Pick Normal Grid for speed.
• Supports that don’t touch the visible face: pick whatever uses less material.
• Total print time under 30 minutes: the slicing-time difference is seconds and the material difference is grams. Don’t sweat it.

I’ve watched myself spend 20 minutes deciding between Slim and Organic on a print I was going to glue inside a project box. The right answer was “stop deciding, hit slice.”

Frequently asked questions

Is Organic the same as Tree?

No, but it’s the current default tree style in OrcaSlicer. Tree is the family name covering Organic, Slim, Strong, and Hybrid. Organic is one specific implementation, derived from Thomas Rahm’s Cura algorithm via PrusaSlicer 2.6.

Can I mix Normal and Tree on one object?

Not directly through a per-region style setting yet. Hybrid tries to do this automatically and is broken. The current workaround is paint-on supports. Discussion #8076 tracks the feature request.

Why is Tree Hybrid in the dropdown if it doesn’t work?

It was implemented and shipped, and the maintainers haven’t removed it. Issue #6618 was closed “not planned” rather than reverted. For 2026 I’m treating it as deprecated.

Do tree supports work with adaptive layer height?

Tree Slim and Tree Strong yes. Organic no, despite the UI option being present. Issue #11215 is the clearest report. If you want both, use Slim.

Should I use 2 or 3 interface layers?

Two is the Orca default and works for most prints. Bump to three when the overhang surface is rough after removal, or in materials that are hard to bridge cleanly.

Why are my Organic supports printing in mid-air?

Either adaptive layer height is on (Organic doesn’t support it) or a trunk has cracked. If neither, check that On Build Plate Only isn’t accidentally enabled; that flag prevents trees rooting on the model surface, leaving deep recesses unsupported.

Does fuzzy skin interact with supports?

Only on the surface that gets fuzzy skin. Supports themselves don’t go fuzzy. If you’ve enabled fuzzy skin on a face that also has supports, pick the cleanest support style you can (Organic) and use a higher Top Z Distance.

Cheat sheet

Screenshot this block.

• Default tree style: Organic
• Default normal style: Grid
• Top Z Distance starting point: 0.20mm (PLA), 0.25mm (TPU), 0.15mm (ABS)
• Threshold angle: 45 to 50 (PLA), 50 to 55 (PETG), 35 to 40 (ABS / ASA)
• Interface layers: 2 (3 if rough)
• Skip: Tree Hybrid
• For adaptive layer height: Tree Slim
• For multi-color soluble: Normal Grid
• For figurines, busts, miniatures: Organic
• For brackets, plates, enclosures: Normal Grid
• For 0.6mm or 0.8mm nozzles: Normal Grid or Tree Strong
• For time-critical iteration: Normal Grid

Where to go next

If you came in cold and want the wider context, our OrcaSlicer settings master guide is the pillar this article hangs under. For the deeper algorithmic and parameter tuning details on tree supports specifically, the tree supports deep dive picks up where this article ends. Sibling cluster articles you’ll probably want next:

• Adaptive layer height if you’re combining variable LH with Tree Slim.
• Fuzzy skin for surface texture work that interacts with support placement.
• Brim, raft, and skirt for fixing tree-foot detachment.
• Multi-color print guide for soluble support workflows.
• Bambu AMS guide for PVA and BVOH on AMS-equipped printers.
• Troubleshooting master for failures that aren’t support-specific.
• Temperature tower for the calibration step that lets you raise threshold angle safely.
• Filament settings for the per-material tuning that drives Top Z Distance.

One last thought. I keep landing on the same workflow: Organic for sculpted, Normal Grid for mechanical, Tree Slim when adaptive layer height is on. That covers about 95% of my prints. The other 5% I figure out by slicing twice and comparing previews. That’s free information, and it usually settles the argument faster than another forum thread.

Related OrcaSlicer guides

• OrcaSlicer vs Bambu Studio: Which Is Better in 2026?
• OrcaSlicer vs Cura: Speed, Calibration & Compatibility (2026)
• OrcaSlicer vs Anycubic Slicer Next: Which Fork Wins for Kobra?
• OrcaSlicer Arachne vs Classic Wall Generator: Which Wins?
• OrcaSlicer Slow Slicing on Complex Models: How to Speed Up