3ds Max Units Setup: Lock System Units Before You Model or Import

Two scenes can show the same number at different real sizes

3ds Max separates the scale geometry is stored at from the scale the interface reports. System Units define how one scene unit maps to a real-world measurement. Display Units only change how measurements appear in spinners, the Tape helper readout, and other UI fields. A length field reading 100 could mean 100 inches or 100 centimeters depending on the scene's System Units, so the number alone never tells you the true size.

The useful takeaway: decide the System Unit convention before the first object exists, record it for the project, and verify it with a measured primitive plus one known-scale asset from the receiving pipeline. Changing System Units on a finished scene reinterprets existing geometry rather than converting it, which is why this is a scene-start decision instead of a mid-project toggle.

Prerequisites before you touch Units Setup

• Agree on a convention with whoever consumes the output. Engine-bound assets commonly use centimeters or meters; architectural work commonly uses inches or millimeters. Confirm whether the target expects 1 unit = 1 meter or a different base.
• Obtain at least one reference asset whose real dimensions you already know, ideally from the same pipeline that will receive your export.
• Confirm the exact menu paths and dialog wording in your installed release. Labels and import-conversion options differ between versions and between standard and extended importers, so treat any path below as a starting point to check locally.

System Units versus Display Units

Aspect	System Units	Display Units
What it controls	Stored geometry scale and real-world mapping	Numeric readout in the UI only
Effect on existing objects	Reinterprets them when changed later	None on geometry
Typical use	Set once at scene start	Set for convenient reading

Procedure: set units at scene start

1. Open Customize > Units Setup. Verify the wording in your release before relying on it.
2. Set System Unit Scale first. This is the value that determines real size, so it should match the convention you agreed on.
3. Set Display Units second, choosing whatever readout scale is easiest to work with. Because Display Units do not affect geometry, you can change them later without risk.
4. If your release supports saving a scene template or a default UI scheme that carries unit settings, use it so new scenes inherit the convention instead of relying on memory. Confirm this behavior in your version before depending on it.
5. Record the convention somewhere the whole team can read it. A short project note is enough:

Project: engine-bound props
System Units: centimeters
Display Units: centimeters
Export target: 1 unit = 1 cm
Reference asset: crate_1m.max (known 100 cm)

Import and merge: conversion or reinterpretation

When content arrives from another file, the merge and import dialogs — together with the Units Setup option governing whether incoming files respect their own system units — determine whether that content is converted into the host scale or reinterpreted at its raw numbers. These two outcomes look similar in the viewport but produce different real dimensions.

Decide deliberately per asset source. If a library asset is authored in meters and your scene is in centimeters, you want conversion. If you are merging a file that is already in your convention, conversion is a no-op and reinterpretation is harmless. The failure mode is leaving the setting on a default that does not match the source.

Checks that catch a mismatch

1. Open Units Setup and read the System Unit Scale value. Confirm it matches the agreed convention before modeling begins.
2. Create a primitive of a known size, then measure it with the Tape helper or the Measure utility. Confirm the reported real-world dimension equals the intended dimension.
3. Import or merge one known-scale reference asset and measure it in the host scene. This catches silent rescaling that a viewport glance will not reveal.
4. Export a test asset to the target format, open it in the receiving tool, and confirm its dimensions match the source. This is the only check that catches mismatches invisible inside 3ds Max.
5. After any rescale operation, step through animation keys and any simulation or physics setup to confirm timing and behavior were not distorted.

Recovery when an asset arrives at the wrong scale

The Rescale World Units utility, reached through the Utilities panel and its More button, applies a scale factor to the whole scene or to a selection. It is the fastest fix for a uniformly wrong scene.

Treat it as a corrective tool rather than a routine step. It can affect modifiers, animation keys, and some procedural or physics parameters inconsistently, so re-check animation timing and simulation setup afterward. When only a few objects are wrong, re-importing the source asset with the correct conversion is the cleaner fallback. When the wrong object is an XRef scene, XRef object, or Container, fix the source file instead — referenced content inherits the host scene's unit context, so patching the assembled scene leaves the source still wrong for the next person.

Limitations and version-specific details to confirm

• Exact menu paths, dialog labels, and import-conversion options vary between 3ds Max releases and between standard and extended importers. Verify each one in your installed build.
• Unit conversion on import is not always lossless for rigged, simulated, or constrained content. Prefer correcting the source file when a referenced asset is wrong.
• Display Units remain misleading as a scale check no matter how the scene is configured. Always confirm real size through measurement or through the receiving tool.
• The behavior of scene templates and default UI schemes with respect to unit settings should be confirmed against your version's documentation before you rely on it for team-wide consistency.