What Is a DGN File?
A .DGN file (Design file) is the native drawing format for MicroStation, made by Bentley Systems. Think of it as MicroStation's equivalent of AutoCAD's .DWG file — it stores all the geometry, annotations, levels (layers), and settings for a drawing.
The name comes from "Design" — Intergraph Corporation (later Bentley) created the format in the 1980s, and it has been the standard for MicroStation ever since.
You don't need MicroStation to work with DGN files. AutoCAD has had built-in DGN support since AutoCAD 2007, so you can attach, import, and even export DGN files without ever opening MicroStation.
Who Uses DGN Files — and Why Will You Encounter Them?
DGN files are most common in industries where government agencies set the CAD standard. If you work with any of the following, you will encounter DGN:
🏛 Government & DOT
- State Departments of Transportation (CalTrans, TxDOT, FDOT, etc.)
- Federal Highway Administration (FHWA)
- US Army Corps of Engineers
- Federal Transit Administration
- Airport Authorities (FAA-related projects)
- Port Authorities and waterway projects
- Many municipalities and counties
🏗 Industries
- Civil / transportation engineering firms with DOT clients
- Bridge and highway design
- Rail and transit (light rail, subway, commuter rail)
- Utility companies (some use MicroStation for GIS/mapping)
- Petrochemical and process plant design
- Offshore oil & gas platforms
- Mining and industrial facilities
DGN vs DWG — The Plain English Comparison
Both formats do the same job — store CAD drawings. The key difference is which software created them. Here's what that means in practice:
| Feature | DGN (MicroStation) | DWG (AutoCAD) |
|---|---|---|
| Made by | Bentley Systems (formerly Intergraph) | Autodesk |
| Software | MicroStation, OpenRoads, OpenBridge, InRoads | AutoCAD, Civil 3D, Map 3D, Revit |
| File extension | .dgn | .dwg |
| Layers called | Levels (V7: 0–63 numbered · V8: named) | Layers (always named) |
| Blocks called | Cells (stored in cell libraries) | Blocks (stored in the drawing) |
| Xrefs called | Reference Files (attached models) | Xrefs (external references) |
| Selecting objects | Element Selection, Fence | Selection Window, Crossing Window |
| Polyline equivalent | SmartLine, Complex Chain | Polyline (PLINE) |
| Hatch equivalent | Pattern (area fill) | Hatch (BHATCH) |
| Coordinates | Uses Global Origin + Master/Sub-Units | World Coordinate System (WCS) |
| Colors | 255-color table (similar to ACI but different) | AutoCAD Color Index (ACI) 1–255 + True Color |
| 3D support | Yes — full 3D modeling | Yes — full 3D modeling |
| Market share | Strong in government, DOT, infrastructure | Dominant in AEC, utilities, commercial |
| Learning curve | Steep — very different interface from AutoCAD | Familiar (if you're already here) |
DGN Terminology Translator — MicroStation → AutoCAD
The biggest confusion when first encountering DGN files is the different names for the same concepts. Here's the complete translator:
| MicroStation Term | AutoCAD Equivalent | Notes |
|---|---|---|
| Level | Layer | V7 DGN: numbered 0–63 only. V8: unlimited named levels — much closer to AutoCAD layers |
| Cell | Block | Cells are stored in separate Cell Library files (.cel) rather than embedded in the drawing |
| Cell Library (.cel) | Block library / WBLOCK collection | A separate file containing reusable cell definitions |
| Reference File | Xref (external reference) | DGN files can reference other DGN files as background geometry |
| Model | Layout tab / Modelspace | A DGN file can contain multiple models (design models + sheet models) |
| Design Model | Model Space | Where the actual geometry lives, at real-world scale |
| Sheet Model | Paper Space / Layout | The plotted sheet, with saved views (like viewports) placed on it |
| Saved View | Named View | Saved camera position; in Sheet Model used like a viewport |
| Fence | Selection Window / Crossing Window | A temporary boundary for selecting or cutting elements |
| AccuDraw | Dynamic Input (F12) | Coordinate entry assistant — MicroStation's version of Dynamic Input |
| SmartLine | PLINE (Polyline) | Creates connected line/arc segments |
| Complex Chain | Open Polyline | A connected open series of elements |
| Complex Shape | Closed Polyline / Region | A closed connected series of elements |
| B-spline Curve | Spline (SPLINE) | Free-form curve through control points |
| Pattern | Hatch (BHATCH) | Area fill with repeating patterns |
| Text Node | Mtext or Dtext | Multi-line text with alignment origin |
| Dimension | Dimension | Same concept — different style settings |
| Line Style | Linetype | DGN has 8 built-in line styles + custom |
| Line Weight | Lineweight | DGN uses weights 0–31 mapped to mm values |
| Active Color | Current Color (CECOLOR) | The color used for new elements |
| Seed File | Drawing Template (.dwt) | A blank DGN with predefined units, levels, and settings — used to start new drawings |
| DGN Library | Block Library / Tool Palette | A DGN file used to store shared resources |
| Raster Reference | Image Attach (IMAGEATTACH) | An attached image file as a background |
| Working Units | Drawing Units (UNITS) | Master Units + Sub-Units define the measurement system |
| Element | Object / Entity | MicroStation calls everything an "element" |
| Tag | Attribute (ATTDEF) | Text data attached to a cell |
| Project Workspace | Network Template / Profile | Centralized standards settings for a project or firm |
Opening a DGN File in AutoCAD — Your First Steps
When someone sends you a DGN file, you have two main options in AutoCAD: attach it as an underlay (best for using it as a background reference) or import it (converts geometry to native AutoCAD objects). Here's how to decide:
✓ Use DGNATTACH when:
- You just need to trace over or reference the DGN geometry
- You don't need to edit the DGN content
- The DGN file will be updated by others and you want live changes
- File size is a concern (underlay is just a reference, not geometry)
- You're doing a quick background check
✓ Use DGNIMPORT when:
- You need to edit specific elements from the DGN
- You're building a permanent DWG from DGN data
- You need to plot DGN geometry in a specific CTB/STB style
- The DGN file is a one-time transfer (final as-built, etc.)
- You need AutoCAD commands to work on those elements
DGNATTACH — Attaching a DGN File as an Underlay
Just like XATTACH attaches a DWG file, DGNATTACH attaches a DGN file as a non-editable underlay. The geometry displays in your drawing but stays in the original DGN file.
Step-by-Step: Attaching a DGN Underlay
DGNATTACH at the command line and press Enter. The Select DGN File dialog opens.DGNLAYERS to open the DGN Levels panel. You can turn individual DGN levels on/off without editing the original file — exactly like freezing layers.DGNSNAP and set to 0 to disable. Turn it back on with DGNSNAP 1.
DGNIMPORT — Converting DGN Geometry to AutoCAD Objects
DGNIMPORT reads a DGN file and creates native AutoCAD objects from the DGN elements. Lines become Lines, text becomes MText, levels become Layers. This is a one-time translation — the DGN file is not linked afterward.
Step-by-Step: Importing a DGN File
DGNIMPORT and press Enter. The Import DGN File dialog opens.AUDIT and PURGE after any DGN import.
What Translates — and What Doesn't
| DGN Element | AutoCAD Result | Notes |
|---|---|---|
| Line, Arc, Circle, Ellipse | Line, Arc, Circle, Ellipse | Translates cleanly |
| SmartLine / Complex Chain | Polyline or Lines | May explode into individual segments |
| Complex Shape | Closed Polyline or Region | Usually translates as polyline |
| B-spline Curve | Spline | Translates cleanly |
| Text | MText or Text | Font may substitute; special characters may drop |
| Dimension | Dimension | Style settings may need adjustment |
| Cell (instance) | Block Insert | Cell definition becomes a Block |
| Pattern (hatch) | Hatch | Standard patterns translate; custom may not |
| Level | Layer | Level name/number → Layer name |
| Line Style (custom) | Continuous or approximate Linetype | Custom DGN line styles often become continuous |
| Reference Files | Xrefs or embedded geometry | Optionally included in import — may need separate import |
| Raster Reference | Not imported | Attached images are not transferred |
| Sheet Model | Not imported by default | Only the selected model is imported at a time |
DGNEXPORT — Sending AutoCAD Drawings to DGN Format
When a client or agency requires you to deliver drawings in DGN format, use DGNEXPORT. AutoCAD translates the DWG content into a DGN V8 file.
Level Mapping — Controlling How DGN Levels Become AutoCAD Layers
By default, AutoCAD translates DGN level names directly to AutoCAD layer names. But in practice — especially with V7 DGN files where levels are numbers (1, 2, 3...) — you often need to map DGN levels to specific AutoCAD layer names, colors, and linetypes. This is done with a .dgnmapping file.
The .dgnmapping File
A DGN mapping file is an XML file that tells AutoCAD how to translate between DGN and DWG properties during DGNIMPORT and DGNEXPORT. You create and manage mapping files with the DGNMAPPING command.
Example Level Mapping Table (V7 DOT Standard)
| DGN Level | DOT Use | → AutoCAD Layer | Color | Linetype |
|---|---|---|---|---|
| 1 | Right of Way Line | ROW-LINE | 1 (Red) | PHANTOM |
| 2 | Existing Centerline | CL-EXIST | 3 (Green) | CENTER |
| 3 | Proposed Centerline | CL-PROP | 2 (Yellow) | CENTER |
| 5 | Existing Edge of Pavement | EP-EXIST | 7 (White) | Continuous |
| 10 | Existing Contours (Major) | CONTOUR-MAJ | 4 (Cyan) | Continuous |
| 11 | Existing Contours (Minor) | CONTOUR-MIN | 4 (Cyan) | Continuous |
| 20 | Survey Points | SURVEY-PT | 6 (Magenta) | Continuous |
| 63 | Annotation / Notes | ANNO-TEXT | 7 (White) | Continuous |
Note: Actual DOT level standards vary by state and project. Always check the project's CAD standards manual for the official level-to-layer mapping.
DGN Units — Master Units and Sub-Units
DGN files use a two-tier unit system that is different from AutoCAD's single drawing-unit system. Getting this right is critical for correct scaling when importing or attaching DGN files.
How DGN Units Work
Master Units (MU) are the primary measurement unit — like feet or meters. Sub-Units (SU) are the subdivision of the master unit — like inches within feet, or millimeters within meters. Positional Units (PU) are the internal precision units that MicroStation uses for calculations.
| Common DGN Setup | Master Unit | Sub-Unit | PU per SU | Equivalent AutoCAD INSUNITS |
|---|---|---|---|---|
| US Survey (Imperial) | Feet (1 MU = 1 ft) | Inches (12 SU = 1 MU) | 8000 | INSUNITS = 2 (feet) or 1 (inches) |
| Metric (Civil/DOT) | Meters (1 MU = 1 m) | Millimeters (1000 SU = 1 MU) | 1000 | INSUNITS = 6 (meters) or 4 (mm) |
| Decimal (Survey) | Feet | Feet (no subdivision) | 10000 | INSUNITS = 2 (feet) |
| Architectural (US) | Inches | Fractional inches | 8000 | INSUNITS = 1 (inches) |
DGN File Versions — V7 vs V8 vs V8i
There are two distinct DGN file formats. Knowing which version you have determines what features are available and how well AutoCAD can translate the content.
| Version | MicroStation Release | Max Levels | Level Names | AutoCAD Support |
|---|---|---|---|---|
| V7 (Pre-V8) | MicroStation 95, SE, J (before 2004) | 63 numbered levels | Numbers only (1–63) | Good — all basic geometry imports |
| V8 | MicroStation V8 (2004+) | Unlimited | Named levels (like AutoCAD layers) | Excellent — closest to DWG format |
| V8i | MicroStation V8i SS1–SS10 | Unlimited | Named + level libraries | Very good — same as V8 for basic use |
| CONNECT | MicroStation CONNECT (2016+) | Unlimited | Named + model management | Good — use V8 export target in AutoCAD |
Key V7 Limitations You'll Hit
- Only 63 levels — complex drawings may have everything squeezed onto a few levels, making layer mapping difficult
- Level names are numbers, not descriptive — you need the project's CAD standards document to know what Level 5 means
- No embedded level descriptions — you can't look at the DGN to understand the level purpose
- Cell libraries are separate files — cells in a V7 DGN may not resolve unless the original .cel files are present
- Custom line styles often don't translate — they typically come in as Continuous
Multi-Model DGN Files
Unlike DWG files which have one Model Space and multiple Layout tabs, a single V8 DGN file can contain multiple completely separate models. A typical DOT project DGN might contain:
| Model Type | Contents | AutoCAD Equivalent |
|---|---|---|
| Design Model (3D) | Real-world geometry at 1:1 scale, full 3D | Model Space |
| Design Model (2D) | 2D plan geometry at 1:1 scale | Model Space |
| Sheet Model | The plotted sheet at paper size, with saved views placed as viewports | Paper Space Layout |
| Drawing Model | Detail or callout views separate from the main design | Separate Layout or Detail Xref |
When you DGNATTACH or DGNIMPORT, you select which model to bring in. You can only process one model at a time. For a DOT bridge project, you might need to separately import the Plan model, the Profile model, and the Cross-Section model — each stored as a separate model in the same DGN file.
Government / DOT Workflow — Working with DGN on Real Projects
State DOTs typically require that all roadway design drawings be prepared or delivered in MicroStation DGN format to their specific standards. Here's how that workflow typically intersects with AutoCAD:
Scenario 1: You Receive DOT Background DGN Files
The DOT provides you with base map DGN files (survey, existing road geometry, right-of-way) and you need to overlay your utility/structural design on them.
Scenario 2: You Receive a DGN That Needs to Become a DWG
The project was done in MicroStation and you're taking it over in AutoCAD, or a subcontractor delivered DGN files and you need them as DWG for your drawing set.
DGN System Variables
These system variables control how DGN underlays display and behave. They work like the equivalent DWF/PDF underlay variables.
Common DGN Problems and Fixes
| Problem | Likely Cause | Fix |
|---|---|---|
| DGN is 12× too big or too small | Unit mismatch: feet vs inches | Re-attach/re-import with "1 Master Unit = 12 Drawing Units" or 0.0833. Check DGN master unit setting. |
| DGN is 25.4× wrong scale | Metric/imperial mix: mm vs inches | Set "1 Master Unit = 25.4 Drawing Units" or 0.03937. |
| Geometry is at wrong location (miles away) | State Plane Coordinates in DGN | DOT files use State Plane coordinates — huge values. Re-attach with DGNCLIP to frame area of interest, or use DGNIMPORT and move the geometry to the origin. |
| Custom line styles show as continuous | DGN custom line styles not supported | Known limitation. Map DGN line styles to AutoCAD linetypes in the .dgnmapping file, or manually change after import. |
| Text appears garbled or missing | DGN uses fonts not installed in AutoCAD | Install the MicroStation font library or substitute fonts in the mapping file. RSC (Resource) font files from MicroStation may be needed. |
| Cells didn't convert to blocks | V7 cell library (.cel) not accessible | The cell library file must be in the same folder as the DGN. Request the .cel files from the sender. Without them, cells may import as geometry. |
| DGN levels not showing in DGNLAYERS | Model has no named levels | V7 DGN levels are numbered. DGNLAYERS shows numbered levels — check "Show all levels" checkbox in the panel. |
| DGN underlay disappears when printing | DGNFRAME = 1 or 0, not 2 | DGN underlays DO plot — the DGN geometry plots, not just the frame. If geometry doesn't plot, check the Plot options in Page Setup and make sure "Plot all objects" is selected. |
| Reference files in DGN not visible | DGN reference files not co-located | The DGN file references other DGN files. Get all referenced DGN files in the same directory. Then re-attach — AutoCAD resolves relative paths automatically. |
| DGNEXPORT output looks wrong in MicroStation | No seed file / wrong seed file used | Always use the client's seed file when exporting for DOT submission. Request the project's .dgn seed file from the agency CAD coordinator. |