Explainer · cad block naming conventions
CAD block naming conventions, explained
By Saumyajit Maity · Published 1 Feb 2023 · Updated 3 Feb 2026
A naming convention is the cheapest productivity tool in CAD. It costs nothing to adopt, and it pays back every single time you or a colleague searches for a block, sorts a folder, or tries to make sense of someone else's drawing. Get it right and 'where's that 700 door?' is a two-second answer. Get it wrong — or have no convention at all — and your library slowly fills with chair3, NEW chair, and chair-FINAL-actually-final.
This guide explains how to name CAD blocks (and their files) so they sort sensibly, search predictably, and stay readable as the library grows into thousands of entries. There's no single 'correct' standard — different firms and standards bodies use different schemes — but they all share the same underlying logic, and that logic is what's worth understanding.
We'll cover why names matter more than people expect, a practical field-order pattern, how block names relate to file names and layer names, the well-known industry standards, and the pitfalls that quietly wreck an otherwise tidy library.
Why block names matter more than you'd think
A block name is metadata that travels with the geometry forever. It shows up in the Blocks palette, in DesignCenter, in block tables, in any schedule you extract, and in the file browser if the block is its own DWG. Unlike a comment or a note, you can't ignore it — every drafter who touches the drawing reads it. A clear name is a tiny gift to every future user; a name like 'Block17' is a tiny tax.
Names are also your search and sort index. Type 'door' into a file browser and good names surface every door together; bad names scatter them. Sort a folder alphabetically and a consistent field order groups all the chairs, then all the desks, then all the tables. The whole point of a convention is to make the computer do your filing for you, automatically, every time.
Field order: object, type, size, view
The most robust pattern puts the broadest category first and narrows from there, because alphabetical sorting then clusters related blocks. A reliable order is object - type - size - view, for example CHAIR-TASK-600-PLAN or DOOR-SINGLE-900-ELEV. The leading word is the thing you search for; the trailing fields disambiguate.
Leading with the object type is the key decision. CHAIR-TASK and CHAIR-EXEC sort next to each other; TASK-CHAIR and EXEC-CHAIR scatter across the alphabet. Include the defining dimension when it matters — door and window widths, appliance modules — because size is often exactly what distinguishes two otherwise identical blocks. Append the view (PLAN, ELEV, SECT) when the same object ships multiple views, so you can tell at a glance which one you're grabbing.
Separators, case and length
Use a single, consistent separator — hyphens or underscores — and never spaces. Spaces break command-line and scripting workflows, sort inconsistently, and look broken in some dialogs. Pick one case (uppercase reads well for block names, lowercase for file names is common) and apply it everywhere; mixed case means the same name can sort in two places on case-sensitive systems.
Keep names as short as they can be while staying unambiguous. A name is a label, not a description — DOOR-DBL-1500-ELEV beats DOUBLE-GLAZED-ENTRANCE-DOOR-FIFTEEN-HUNDRED-ELEVATION. Use a small set of agreed abbreviations (DBL, SGL, ELEV, SECT, PV for plan view) and write them down so everyone expands them the same way. Avoid characters that some filesystems or older software dislike: slashes, colons, asterisks and the like.
Block names, file names and layer names together
Three naming systems sit next to each other and ideally agree. The file name (when a block is its own DWG), the internal block-definition name, and the layer names the block uses. The cleanest setup makes file name and block name match — DOOR-SGL-900.dwg containing a block named DOOR-SGL-900 — so the name you see in the browser is the name you see in the Blocks palette.
Layer naming deserves its own convention, and the big standards bodies define one. The point is that layer names carry meaning too — a layer like A-DOOR or L-PLANT tells you the discipline and the content. When your block names and your layer names follow compatible patterns, a drawing becomes self-documenting: you can read its structure from the names alone, without opening anything.
Standards you can borrow
You don't have to invent a scheme from scratch — mature standards exist and are worth borrowing from. The US National CAD Standard (NCS), built on the AIA CAD Layer Guidelines, defines a structured layer-naming system (discipline code, major group, minor group, status) that many North American firms follow. In the UK and much of the Commonwealth, BS 1192 and its successors set out layer and file naming for collaborative production. ISO 13567 is the international standard for layer organisation.
For block names specifically there's less formal standardisation, so most firms define a house style that rhymes with whichever layer standard they use. The pragmatic move is to adopt or adapt an existing standard rather than fight one into existence: it's already been thought through, new staff may already know it, and consultants you exchange files with are more likely to recognise it.
Pitfalls that wreck a naming scheme
A few habits quietly undo even a good convention. Version noise is the worst: chair-v2, chair-new, chair-USE-THIS. These are a symptom of having no single source of truth — fix the library so there's one canonical block, don't encode the chaos into names. Inconsistent abbreviations are next: ELEV in some names, EL in others, ELEVATION in a third, so a search for any one misses the others. Agree the abbreviations once and publish them.
Watch for ambiguous leading words, too — naming a block 'MODERN' or 'TYPE-A' buries the actual object and defeats sorting. And beware silent renaming on insertion: if you insert a DWG whose internal block name clashes with an existing block, AutoCAD may keep the existing definition, so two different 'CHAIR' blocks can collide. Unique, descriptive names prevent that. The overarching pitfall is simply letting the convention lapse — a standard only works while everyone actually follows it, which is why writing it down beside the library matters as much as choosing it.
Free download
Browse the full library — DWG & DXF, no signup.
Questions
Frequently asked
What's a good naming pattern for CAD blocks?+
Object first, then type, size and view: CHAIR-TASK-600-PLAN, DOOR-SINGLE-900-ELEV. Leading with the object groups related blocks when you sort or search. Use a single separator (hyphen or underscore), no spaces, consistent case, and a small set of agreed abbreviations.
Should the block name match the DWG file name?+
Ideally yes. If DOOR-SGL-900.dwg contains a block named DOOR-SGL-900, the name you see in the file browser matches the one in the Blocks palette and DesignCenter, which keeps everything findable and avoids confusion when you insert it.
Are there official CAD naming standards I can follow?+
Yes. The US National CAD Standard (built on the AIA CAD Layer Guidelines) is widely used in North America; BS 1192 and its successors cover UK collaborative production; and ISO 13567 is the international layer-organisation standard. Most firms adopt or adapt one rather than inventing their own.
Why shouldn't I use spaces in block or file names?+
Spaces break command-line and scripting workflows, can sort inconsistently, and render awkwardly in some dialogs and on some systems. Use a single consistent separator — a hyphen or underscore — instead, so names behave the same everywhere they're read.
What happens if two blocks have the same name?+
When you insert a DWG whose internal block name matches an existing block in the drawing, AutoCAD typically keeps the existing definition rather than overwriting it — so you can end up with the wrong geometry under a familiar name. Unique, descriptive names avoid this kind of silent clash.
Related downloads
Blocks for this guide
Related categories
Related guides
Explainer
How to Organize a CAD Block Library (DWG)
How to organize a CAD block library that stays usable as it grows — folder structure, naming, units, tool palettes and a shared standard library for teams.
Explainer
What Makes a Good CAD Block? A Practical Checklist
What separates a good CAD block from a junk one — correct units, a sensible base point, clean layers, the right level of detail, and a purged, lightweight file.
Explainer
Are Free CAD Blocks Safe for Commercial Use?
Are free CAD blocks safe to use commercially? The two real questions — licensing and file safety — answered plainly, plus how to vet a block before you ship it.