Blocks
One definition. Many instances. Edit once, update everywhere.
Why this matters
A block is a named symbol definition stored inside the drawing. When you insert a block, you're placing an instance that references the definition — not a copy of the geometry. Change the definition, and every instance in the drawing updates simultaneously. In a planting plan with 40 identical tree symbols, that's the difference between updating one object and updating 40.
Blocks are also the mechanism behind plant symbols, site furniture, north arrows, and most of the standard elements in a production drawing. Knowing how they work — not just how to insert them — means you can use, edit, clean, and create them rather than just hoping they behave.
Block logic
| Concept | What it means in practice |
|---|---|
| Definition vs. instance | The block definition is the geometry stored in the file. An instance is a placed reference to that definition. You can have 1 definition and 500 instances — the file stores the geometry once. |
| INSERT (I) | Places an instance of a block at a specified point, scale, and rotation. The insertion point is the origin (0,0,0) of the block definition — choose this thoughtfully when creating blocks. |
| BLOCK (B) | Creates a new block definition from selected geometry. Define the insertion point carefully — it is what the cursor snaps to when inserting. |
| WBLOCK | Writes a block or selected geometry to an external .dwg file. Used to create a standalone symbol file for the block library. |
| BEDIT | Opens the block definition for editing. Changes propagate to all instances in the drawing. |
| EXPLODE (X) | Breaks a block instance into its component geometry. Use with caution — exploding destroys the link to the definition. All instances of that block in the drawing remain as blocks; only the exploded one becomes raw geometry. |
| Layer 0 rule | Block geometry created on Layer 0 inherits the layer of the layer it's inserted on. Geometry on any other layer within the block definition keeps its original layer regardless of where the block is inserted. |
XREF vs. Block — they are not the same
An XREF is a live link to an external file — it is referenced, not embedded. The survey drawing is an XREF: it lives in your XREF folder, appears in your drawing, and updates when the source file changes. A block is embedded within the current drawing file. It has no external dependency. Confusing the two produces file management errors that are difficult to untangle under pressure.
Blocks from the web — proceed with caution
Downloaded blocks almost always carry foreign layers, text styles, and dimension styles that contaminate your drawing. Before using any downloaded block in a production file, open it, explode it, inspect what layers it brought in, reassign geometry to your standard layers, delete the foreign layers, run PURGE, and redefine it as a new block on your standard layer structure. This process takes 10 minutes and prevents hours of problems later.
Try this
Download any AutoCAD plant symbol block from the web. Open it. Explode it. Open the Layer Manager and note every layer that wasn't there before. Note any text styles or linetypes that were imported. Run PURGE and observe what gets removed. Now you understand exactly what every block you download is doing to your file before you clean it.
What breaks
Exploding blocks you need to edit destroys the definition link. All 40 trees you need to change now have to be changed individually. Use BEDIT to edit the definition if you need to change all instances.
Inserting a block with the wrong scale is common when blocks come from files with different units. Use the SC Reference option to scale by a known measurement rather than guessing a factor.
Inserting blocks on the wrong layer and then expecting MATCHPROP to fix the layer: MATCHPROP will move the block instance to a new layer, but the geometry within the block definition still has its own layer assignments. Check inside the block if layer-based display control matters.