<h2>Make sure to set the scale properly for your use case!</h2>
<p>In CAD, you define your measurement space in either Inch or in Millimeter units, and that is your grid. In blender, the native unit is the meter.</p>
<p>This can be easily converted in exporting (remember to set it to scale!), but it is best to just set the measurement scale to actually match what you design: if you want to design a 5 mm hole, set your scale to Millimeters and make sure you export in millimeters. If you want to design in meters (maybe you design a building), then work in meters, and set your export scale in the end so that 1 meter actually is represented as 1 meter - or rather as 1000 millimeters.</p>
<p><a href="https://3dprinting.stackexchange.com/a/7561/8884">The STL in the end will not know the difference</a>: it all is defined in scales of <em>unitary units</em>, and it doesn't even know if it was originally designed in meters, inch or angström. The typical slicer expects the unit to be either millimeters or inch, so any scaling of the exported model that does not result in units equivalent to 1 mm or 24.5 mm is bad procedure - converting between these two types is just scaling the model by 2450%.</p>
<h2>Make sure to design closed manifolds made up of triangles!</h2>
<p>When working with blender, it is very easy to leave the item in a shape that contains multiple intersecting, non-manifold surfaces and areas of inverted surfaces. While <em>interecting shells</em> is not a problem (the slicers can handle those by unionizing the item), the intersection usually covers up the non-manifold areas, making them hard to spot.</p>
<p>As a result, before finalizing your project, I suggest follow this procedure:</p>
<ul>
<li>In Blender, turn on the visual for the normals of surfaces. If an area does not look like a hedgehog after that, the normals in that area are reversed and you need to flip the surfaces there or re-mesh it.</li>
<li>Triangulate the surface using the triangulate modifier. This is to spot artifacts from conversion to STL early and be able to fix them: STL only knows triangles, while blender knows <em>bent</em> n-gons.</li>
<li>Add a new object. A cube with side length 1.</li>
<li>Do a test export to STL with scale 1, which also contains the 1-unit cube as an extra shell.</li>
<li>Import the model into a software such as meshmixer, that has a command to separate shells.</li>
<li>Separate the item to all shells. In Meshmixer this is in analyze, separate shells.</li>
<li>After separating the shells, measure your 1-unit cube. If it is not 1 mm, calculate your scaling factor. It should be a multiple of 10.</li>
<li>Next, you should check each shell for gaps or other errors. In meshmixer, the automatic analyze feature points to these areas with red, blue and magenta lines.</li>
<li>Fix the marked errors in blender, then return to the test export. This time use the proper scaling factor. Repeat until no errors remain.</li>
</ul>

CC BY-SA 4.0
2022-03-27T18:52:16.697Z
2022-04-04T12:09:00.823Z
2022-04-04T12:09:00.823Z
Trish
<p>Being realistic, you only need to make sure that your on screen measurements and your export units are set correctly. That way whatever size you set on screen will be reflected in your print.</p>
<p>For example, I use the MeasureIt plugin to tell me the size on screen, and I set the scale to 0.004 and the units to MM, and when I export to an STL file I set the size to 4. That way Cura Slicer always prints to the exact right size.</p>
<p>You can use whatever scale you want so long as you use the equivalent when you export it. I just use this scale because it's the one used when exporting between Hexagon and DAZ Studio, so I did it as a force of habit.</p>

CC BY-SA 4.0
2022-04-02T12:50:49.853Z
2022-04-02T12:50:49.853Z
Aaargh Zombies
<p>It doesn't matter, you scale it in the slicer or elsewhere. You're not going to slice the STL file in Blender. You'll probably need to do more work to get things print ready outside blender anyway.</p>
<p>So when I use blender I don't even bother checking what units it's using. I don't use it for parts design or tech drawing.</p>

CC BY-SA 4.0
2022-03-29T14:58:49.500Z
"You're going to scale it in the slicer" is not reasonable. Especially parts that have real world function and are designed to interface with other things in the real world should have a correct design size where the unit in the STL is assumed to be millimeters. Model sharing sites where the majority of users get this wrong (and get the axes wrong, etc.) are widely derided as low quality, and rightfully so.
R.. GitHub STOP HELPING ICE
CC BY-SA 4.0
2022-03-29T16:02:27.427Z
@R..GitHubSTOPHELPINGICE obviously you wouldn't then. But organic stuff that isn't a part (as I said in my answer) doesn't matter. I do it all the time.
Kilisi
CC BY-SA 4.0
2022-03-30T00:59:11.403Z
Even if the model is organic and intended to be printable at variable sizes, if the units are wrong such that the object is 10 times larger than a typical bed, or smaller than the nozzle, shipping it like that is at best "unfriendly".
R.. GitHub STOP HELPING ICE
CC BY-SA 4.0
2022-03-30T11:59:51.677Z
Anyone shipping an STL straight from blender of any complexity is asking for trouble. Scale is probably the least of the worries
Kilisi
CC BY-SA 4.0
2022-03-30T12:44:09.423Z
I didn't come here to argue with you. I came here to ask about best practices for doing something right not an argument that doing things right is pointless.
R.. GitHub STOP HELPING ICE
CC BY-SA 4.0
2022-03-30T12:46:52.427Z
Then why are you arguing? If you don't like the answer just downvote or ignore it. Good luck with your printing.
Kilisi
CC BY-SA 4.0
2022-03-29T12:01:44.057Z
2022-03-29T12:01:44.057Z
Kilisi
<p>I've been trying to learn Blender as an additional tool for 3D printing (to prepare more organic or freeform models that don't lend themselves to a CAD style workflow I'm more used to), and one point of confusion I've hit is that Blender's default unit is <em>meters</em>, not millimeters. Apparently in older versions its default was an abstract unspecified &quot;units&quot; with metric-like base-10 grid, but no inherent association to physical scale, but now the default is &quot;metric&quot; with meters as the unit. I've found some tutorials <a href="https://www.youtube.com/watch?v=ZI49VIcISaw" rel="nofollow noreferrer">such as this one</a> for switching to millimeters, but it requires making a number of changes that I'm not sure are in line with what folks consider &quot;best practices&quot; for &quot;modeling for 3D printing with Blender&quot;.</p>
<p>Is there any consensus on the right way to do this? Are there reasons I should prefer to switch back to the abstract &quot;units&quot;, and just treat them as millimeters, versus using &quot;metric&quot; but switching the base unit to &quot;0.0001&quot; (maybe numerical precision reasons?).</p>
<p>I know this question is only borderline on-topic, but I think it is relevant as I'm looking for what the prevailing practice <em>in communities using Blender as a tool for 3D printing</em>, not for opinions of a larger Blender community.</p>

CC BY-SA 4.0
2022-03-26T15:10:45.160Z
Coming from a graphic design background, I've always been of the mindset of starting with whatever units your output will be. If you start with something different then you will have to do some kind of scaling or conversion that could potentially effect the design.
agarza
CC BY-SA 4.0
2022-03-26T15:54:04.707Z
@agarza: Well yeah, I want to design in terms of mm. The question is just what the best way to do this with Blender is. Whether to use "unspecified units" and treat them as mm, or leave it in metric mode where the default unit is an unweildy *meters*, but then work in 0.001 of that.
R.. GitHub STOP HELPING ICE
CC BY-SA 4.0
2022-03-26T20:18:21.340Z
Consider also to make use of the 3D features in the newer versions of Blender, especially those related to manifold checking, intersecting planes/edges. Some model makers are creating for visual intent, while constructing non-printable designs. The results can be impossible to correct by non-blender users.
fred_dot_u
CC BY-SA 4.0
2022-03-26T20:52:54.757Z
@fred_dot_u: I actually do wonder what features Blender has for that, especially for repairing models obtained from other sources that have problems. But that's a different question.
R.. GitHub STOP HELPING ICE
CC BY-SA 4.0
2022-03-30T11:29:35.460Z
Even very old versions of blender have repair options for finding and fixing holes in non-manifold surfaces.
user10489
<3d-models><blender>
Best practices for handling units for 3D printing with Blender
R.. GitHub STOP HELPING ICE
# Best practices for handling units for 3D printing with Blender

(Asked by: username_0 on 2022-03-26)

I've been trying to learn Blender as an additional tool for 3D printing (to prepare more organic or freeform models that don't lend themselves to a CAD style workflow I'm more used to), and one point of confusion I've hit is that Blender's default unit is *meters*, not millimeters. Apparently in older versions its default was an abstract unspecified "units" with metric-like base-10 grid, but no inherent association to physical scale, but now the default is "metric" with meters as the unit. I've found some tutorials [such as this one](https://www.youtube.com/watch?v=ZI49VIcISaw) for switching to millimeters, but it requires making a number of changes that I'm not sure are in line with what folks consider "best practices" for "modeling for 3D printing with Blender".

Is there any consensus on the right way to do this? Are there reasons I should prefer to switch back to the abstract "units", and just treat them as millimeters, versus using "metric" but switching the base unit to "0.0001" (maybe numerical precision reasons?).

I know this question is only borderline on-topic, but I think it is relevant as I'm looking for what the prevailing practice *in communities using Blender as a tool for 3D printing*, not for opinions of a larger Blender community.

**Tags:** 3d-models, blender

> **Comments:**
> **username_1**: Coming from a graphic design background, I've always been of the mindset of starting with whatever units your output will be. If you start with something different then you will have to do some kind of scaling or conversion that could potentially effect the design.  
> **username_0**: @username_1: Well yeah, I want to design in terms of mm. The question is just what the best way to do this with Blender is. Whether to use "unspecified units" and treat them as mm, or leave it in metric mode where the default unit is an unweildy *meters*, but then work in 0.001 of that.  
> **username_2**: Consider also to make use of the 3D features in the newer versions of Blender, especially those related to manifold checking, intersecting planes/edges. Some model makers are creating for visual intent, while constructing non-printable designs. The results can be impossible to correct by non-blender users.  
> **username_0**: @username_2: I actually do wonder what features Blender has for that, especially for repairing models obtained from other sources that have problems. But that's a different question.  
> **username_3**: Even very old versions of blender have repair options for finding and fixing holes in non-manifold surfaces.  

---

## 3 answers

### Answer by username_4 on 2022-03-27. Score: 3

## Make sure to set the scale properly for your use case!

In CAD, you define your measurement space in either Inch or in Millimeter units, and that is your grid. In blender, the native unit is the meter.

This can be easily converted in exporting (remember to set it to scale!), but it is best to just set the measurement scale to actually match what you design: if you want to design a 5 mm hole, set your scale to Millimeters and make sure you export in millimeters. If you want to design in meters (maybe you design a building), then work in meters, and set your export scale in the end so that 1 meter actually is represented as 1 meter - or rather as 1000 millimeters.

[The STL in the end will not know the difference](https://3dprinting.stackexchange.com/a/7561/8884): it all is defined in scales of *unitary units*, and it doesn't even know if it was originally designed in meters, inch or angström. The typical slicer expects the unit to be either millimeters or inch, so any scaling of the exported model that does not result in units equivalent to 1 mm or 24.5 mm is bad procedure - converting between these two types is just scaling the model by 2450%.

## Make sure to design closed manifolds made up of triangles!

When working with blender, it is very easy to leave the item in a shape that contains multiple intersecting, non-manifold surfaces and areas of inverted surfaces. While *interecting shells* is not a problem (the slicers can handle those by unionizing the item), the intersection usually covers up the non-manifold areas, making them hard to spot.

As a result, before finalizing your project, I suggest follow this procedure:

* In Blender, turn on the visual for the normals of surfaces. If an area does not look like a hedgehog after that, the normals in that area are reversed and you need to flip the surfaces there or re-mesh it.
* Triangulate the surface using the triangulate modifier. This is to spot artifacts from conversion to STL early and be able to fix them: STL only knows triangles, while blender knows *bent* n-gons.
* Add a new object. A cube with side length 1.
* Do a test export to STL with scale 1, which also contains the 1-unit cube as an extra shell.
* Import the model into a software such as meshmixer, that has a command to separate shells.
* Separate the item to all shells. In Meshmixer this is in analyze, separate shells.
* After separating the shells, measure your 1-unit cube. If it is not 1 mm, calculate your scaling factor. It should be a multiple of 10.
* Next, you should check each shell for gaps or other errors. In meshmixer, the automatic analyze feature points to these areas with red, blue and magenta lines.
* Fix the marked errors in blender, then return to the test export. This time use the proper scaling factor. Repeat until no errors remain.


---

### Answer by username_5 on 2022-04-02. Score: 0

Being realistic, you only need to make sure that your on screen measurements and your export units are set correctly. That way whatever size you set on screen will be reflected in your print.

For example, I use the MeasureIt plugin to tell me the size on screen, and I set the scale to 0.004 and the units to MM, and when I export to an STL file I set the size to 4. That way Cura Slicer always prints to the exact right size.

You can use whatever scale you want so long as you use the equivalent when you export it. I just use this scale because it's the one used when exporting between Hexagon and DAZ Studio, so I did it as a force of habit.


---

### Answer by username_6 on 2022-03-29. Score: -1

It doesn't matter, you scale it in the slicer or elsewhere. You're not going to slice the STL file in Blender. You'll probably need to do more work to get things print ready outside blender anyway.

So when I use blender I don't even bother checking what units it's using. I don't use it for parts design or tech drawing.

> **Comments:**
> **username_0**: "You're going to scale it in the slicer" is not reasonable. Especially parts that have real world function and are designed to interface with other things in the real world should have a correct design size where the unit in the STL is assumed to be millimeters. Model sharing sites where the majority of users get this wrong (and get the axes wrong, etc.) are widely derided as low quality, and rightfully so.  
> **username_6**: @username_0 obviously you wouldn't then. But organic stuff that isn't a part (as I said in my answer) doesn't matter. I do it all the time.  
> **username_0**: Even if the model is organic and intended to be printable at variable sizes, if the units are wrong such that the object is 10 times larger than a typical bed, or smaller than the nozzle, shipping it like that is at best "unfriendly".  
> **username_6**: Anyone shipping an STL straight from blender of any complexity is asking for trouble. Scale is probably the least of the worries  
> **username_0**: I didn't come here to argue with you. I came here to ask about best practices for doing something right not an argument that doing things right is pointless.  
> **username_6**: Then why are you arguing? If you don't like the answer just downvote or ignore it. Good luck with your printing.  

---

