Explainer · block vs xref
Block vs xref: what's the difference?
By Saumyajit Maity · Published 7 Mar 2024 · Updated 7 Mar 2024
Blocks and external references (xrefs) both bring outside drawing content into your file, and both let you place that content as a single, manageable unit. The difference is where the content lives. A block is copied into your drawing and stored inside it — self-contained but frozen at the moment you inserted it. An xref is linked to your drawing — the actual geometry stays in a separate DWG file on disk, and your drawing just displays a live window onto it.
That distinction drives everything else. Because a block is embedded, your file is portable but won't update if the source changes. Because an xref is linked, it updates whenever the source file changes and keeps your file small — but break the link or move the source and the reference goes missing. Choosing wrong leads to two classic headaches: drawings that quietly fall out of sync, or files that won't open with their references intact.
This guide separates the two cleanly: what each is, how they behave on update and on transfer, when professionals reach for each, and how to convert between them when a project needs the other one.
A block is embedded; an xref is linked
When you INSERT a DWG as a block, AutoCAD copies that drawing's geometry into your file's block table and places a reference to it. The content now belongs to your drawing — it travels with the file, opens without anything external, and is completely under your control. But it is a snapshot: if the original source DWG changes later, your block does not, because it is no longer connected to that source.
When you attach a DWG as an xref (with XREF / XATTACH), AutoCAD does not copy the geometry in. It records a path to the external file and displays its contents through that link. The geometry physically stays in the other DWG. Your file holds only the reference and a path, so it stays small — but it depends on that external file being present and findable every time the drawing opens.
How each behaves when the source changes
This is the difference that matters most on a live project. Update the master site plan that ten sheets reference as an xref, and all ten sheets pick up the change automatically the next time they reload — one edit, propagated everywhere, with no re-importing. That is precisely why xrefs are the backbone of multi-discipline coordination: the architect's plan can sit under the structural and services drawings as a live, always-current background.
A block does the opposite. Insert a title-block or a detail as a block and it stays exactly as inserted regardless of what happens to the original file. That is perfect when you want stability — a fixed, embedded copy that no upstream edit can disturb — and wrong when you actually wanted the content to track a master. Match the tool to whether you want 'always current' (xref) or 'frozen and self-contained' (block).
File size, portability and the missing-xref trap
Blocks make a drawing self-sufficient: everything is inside, so you can email the single DWG and it opens complete. The cost is size — embedded content adds weight, and reusing the same large drawing as a block in many files duplicates it each time. Xrefs keep each drawing lean by storing only links, which is a huge advantage when many sheets share one heavy background.
The trade-off is the dependency. An xref is only as reliable as its path. Move, rename or forget to send the referenced file and the recipient sees 'xref not found' and a blank where the content should be. Sending an xref-heavy drawing means sending all the referenced files too (the eTransmit command gathers them for you). So blocks favour portability and simplicity; xrefs favour size and live updates, at the price of careful file management.
When to use a block
Use a block for reusable content that you want embedded and stable: furniture, fixtures, symbols, title-blocks, standard details and any library element that should look the same and stay put. Blocks are also the right call for anything you will hand off as a single self-contained file, or any symbol you place many times within one drawing — their compact references and one-edit-updates-all definition are built for exactly that.
In short, blocks suit content you own and control inside the drawing: the kit of parts you assemble a sheet from. The downloadable DWGs across this site are designed to be used exactly this way — insert them as blocks, and they become a permanent, portable part of your drawing and your library.
When to use an xref
Use an xref for shared backgrounds and any content authored and maintained in a separate file that must stay current. The textbook case is a base plan referenced under many sheets, or a consultant's drawing overlaid on yours for coordination: the architect xrefs the survey, the engineer xrefs the architect's plan, everyone works over a live, single source of truth. Edit the master once and every drawing that references it updates.
Xrefs also keep file sizes sane on big projects where the same large background would otherwise be embedded dozens of times. The rule of thumb: if the content is owned by another file or another person and needs to track changes, xref it; if the content is a fixed library part you want baked into this drawing, block it.
Converting between blocks and xrefs
You can move in both directions. To turn an xref into embedded content, open the Xref Manager, select the reference and choose Bind. Binding converts the linked geometry into a block inside your drawing, severing the live link — useful at the end of a project when you want a self-contained archive copy that no longer depends on external files. Binding 'Insert'-style names the resulting block more cleanly than the default 'Bind' option.
Going the other way, if you have a block (or any geometry) you now want to share as a live reference, write it out as a standalone DWG with WBLOCK and then attach that file as an xref in the drawings that need it. A common project lifecycle uses xrefs during the active, collaborative phase for live coordination, then binds them to blocks at issue or archive so the deliverable opens complete on its own.
Free download
Browse the full library — DWG & DXF, no signup.
Questions
Frequently asked
What is the difference between a block and an xref?+
A block is copied and embedded inside your drawing, so it's self-contained but frozen at insertion. An xref links to an external DWG that stays on disk, so it updates when the source changes and keeps your file small — but depends on that file being present.
When should I use an xref instead of a block?+
Use an xref for shared backgrounds or another person's drawing that must stay current — like a base plan referenced under many sheets. Edit the source once and every drawing that references it updates automatically.
Why does my drawing say 'xref not found'?+
The referenced file has been moved, renamed or wasn't sent with the drawing. Xrefs store only a path, so the source DWG must be findable. Use eTransmit to gather a drawing and all its references when sharing.
How do I convert an xref into a block?+
Open the Xref Manager, select the reference and choose Bind. This converts the linked geometry into a block embedded in your drawing and removes the live link — ideal for a self-contained archive copy.
Related downloads
Blocks for this guide
Popular blocks to download
Related categories
Related guides
Explainer
Dynamic Blocks Explained — AutoCAD Guide in 2026
Dynamic blocks explained simply — what they are, how parameters, actions and grips let one AutoCAD block flex into many sizes, and when to use them over plain blocks.
Explainer
Static vs Dynamic Blocks in AutoCAD Compared
Static vs dynamic blocks in AutoCAD — the real difference, the pros and cons of each, when to choose which, and how to convert a static block into a dynamic one.
Explainer
What Are Block Attributes in AutoCAD?
What are block attributes in AutoCAD? Learn how attributes attach editable text and data to a block, how to define them with ATTDEF, and how to extract schedules.