You open a DWG file from a vendor, a subcontractor, or maybe a PDF import you just ran yourself. You click on something. Properties panel says Layer 0. You click on something else. Layer 0. You open the layer manager and there it is: one single layer with every entity in the drawing sitting on it. Dimensions, cut lines, text, construction geometry, centerlines—all of it, piled onto Layer 0 like laundry in a college dorm room.
If you have worked in manufacturing, fabrication, or any discipline that touches CAD files from outside sources, you have seen this. Probably more times than you care to count. And every time it happens, the same sinking feeling: this drawing is going to take an hour to fix before I can do anything useful with it.
You are not alone, and it is not your fault. This is one of the most common problems in the AutoCAD world, and it has been for decades. Let me walk through why it happens, why it matters way more than most people think, and what you can actually do about it.
Why Everything Ends Up on Layer 0
There is no single cause. The Layer 0 problem is more like a family of related issues, and they all lead to the same frustrating result. Here are the most common ones I have seen over the years.
PDF Imports Flatten Everything
This is probably the number one source of the problem today. Someone sends you a PDF of their drawing instead of the DWG. Maybe they do not want you to have their native file. Maybe they exported it from SolidWorks or Inventor and the DWG option was not convenient. Whatever the reason, you end up running PDFIMPORT in AutoCAD.
And PDFIMPORT does its best. It really does. It converts the vector data back into AutoCAD entities—lines, arcs, polylines, text. But here is the thing: a PDF has no concept of layers. A PDF is a visual document. It stores appearance, not intent. So when AutoCAD imports it, every single entity goes to one layer, usually named something like "PDF_Geometry" or just straight to Layer 0. All the layer information that existed in the original drawing? Gone. Evaporated during the export to PDF.
The same thing happens with DXF files that have been round-tripped through non-Autodesk software. Some CAM programs, some older CNC post-processors, and plenty of free CAD viewers will read a DXF and then write it back out with layer data stripped or mangled. You get the geometry, but the organizational structure is lost.
The Vendor Never Set Up Layers
This one hurts because it is so preventable. A surprising number of people—even people who use AutoCAD every day—never bother with layers. They draw everything on Layer 0 because it works. The drawing looks right on screen, it prints fine, and if they are just handing off a flat 2D drawing for a quote, nobody complains.
Until someone downstream needs to actually use that drawing for manufacturing. Then every entity needs to be identified, classified, and assigned to the correct layer so the CAM software can interpret it properly. The vendor did not do that work because, from their perspective, the drawing was finished.
Legacy Drawings From Older Software
I have opened drawings that were originally created in software that predates AutoCAD’s modern layer system. Drawings migrated from old MicroStation files, from ancient versions of TurboCAD, from some unnamed DOS-era drafting program that a machine shop ran in 1994. These files have been converted and reconverted so many times that whatever layer structure they once had is long gone.
You also see this with drawings that have been passed through multiple companies over the years. Company A makes the original drawing with their layer standard. Company B opens it, does not have those layers in their template, and just drags everything to Layer 0 so their system does not complain. Company C receives it and now has no idea what was what.
Block Inserts With ByBlock Properties
This one is sneaky. If someone creates a block with all entities on Layer 0 and properties set to ByBlock, the entities inside the block inherit the layer of whatever layer the block reference is inserted on. If that block gets exploded, everything drops to Layer 0 with ByBlock color and linetype—meaning it all looks the same and there is no way to distinguish entity types visually.
I have seen entire drawings that were one giant block reference. Someone explodes it, and suddenly a clean drawing turns into a Layer 0 disaster.
Why This Matters for Manufacturing
If you are working in an office where drawings are just for visual reference—a picture to look at—then Layer 0 is annoying but survivable. You can still read dimensions off the screen, you can still print it.
But in manufacturing, layers are not organizational decoration. They are functional. They carry information that downstream software reads and acts on. And when that information is wrong or missing, physical things go wrong.
CAM Software Reads Layers, Not Your Intentions
When a drawing goes from AutoCAD to a laser cutting program, a waterjet controller, or a CNC router’s CAM software, the software does not look at your drawing the way a human does. It does not think "oh, that looks like a dimension, I should ignore it." It reads layers. Entities on the CUT layer get cut. Entities on the ETCH layer get etched. Entities on the DIMS layer get ignored.
When everything is on Layer 0, the CAM software has no way to distinguish between a cut contour and a dimension callout. It sees geometry. And unless someone manually goes through and tells the CAM software what to do with each entity, it will try to process all of it.
The Real Cost: Scrap Parts
I have personally seen dimension text laser-cut into parts because the dimensions were on the same layer as the cut geometry. The laser does not know the difference between a line that forms the edge of a bracket and a line that forms the number "4" in a dimension. They are all just vectors.
One bad drawing can mean:
- Scrapped material (and sheet steel is not cheap)
- Wasted machine time (laser time is billed by the hour)
- Reprogram time to fix the file and re-nest
- Delivery delays to the customer
- An uncomfortable conversation about who is paying for the scrap
Multiply that by the number of drawings that come in the door with Layer 0 problems, and you start to see why this is not a minor annoyance. It is a real cost center.
The Manual Fix (And Why It Does Not Scale)
Alright, so you have a drawing where everything is on Layer 0. Here is how most people fix it by hand.
Step 1: Create Your Target Layers
First, you need the layers to move things to. If you have a template, you open it and copy the drawing into it. If not, you create layers manually: CUT, DIMS, TEXT, CONSTRUCTION, CENTERLINES, BEND, HATCH, and whatever else your shop standard requires.
Step 2: Use QSELECT to Filter by Entity Type
QSELECT is your friend here. You can filter by entity type—select all DIMENSION entities, for example, and move them to the DIMS layer. Then select all TEXT and MTEXT entities and move them to the TEXT layer. Then select all HATCH entities and move them to HATCH.
This gets you maybe 60% of the way there. The easy stuff—dimensions, text, hatches—can be identified by entity type alone.
Step 3: The Hard Part—Lines and Polylines
Here is where it falls apart. The remaining geometry—lines, arcs, polylines, circles—could be anything. A line could be a cut contour. Or it could be a construction line. Or a centerline. Or part of a border. Or a leader line from a dimension that got exploded. QSELECT cannot help you here because the entity type is the same for all of them.
You end up zooming in, selecting entities one by one or in small groups, figuring out what they represent, and assigning them to the correct layer. For a moderately complex drawing, this takes 30 to 90 minutes. For a complex assembly drawing, it can take longer.
Step 4: Verify
After you think you are done, you freeze each layer one at a time and visually check that nothing is misclassified. Did you accidentally put a dimension leader on the CUT layer? Is there a construction line mixed in with the contour geometry? This verification step takes another 10 to 15 minutes if you are thorough.
Total time for one drawing: 45 minutes to over an hour. And you might receive 10 of these in a single day from the same vendor.
A Better Approach: Automated Classification
The manual process I just described boils down to one task: looking at each entity and deciding what it is. Dimension? Move to DIMS. Text? Move to TEXT. Cut geometry? Move to CUT.
The thing is, this decision is not as subjective as it feels. There are rules. A DIMENSION entity is always a dimension. An MTEXT entity is always text. A HATCH entity is always a hatch. For entity types that are ambiguous—like lines and polylines—you can often classify them by looking at other properties: linetype, color, lineweight, or their relationship to other entities.
A line with a CENTER linetype is probably a centerline. A polyline that forms a closed contour with a specific color is probably cut geometry. A line that connects a dimension to the part is a leader.
These rules are not perfect—there will always be edge cases—but they are good enough to handle the vast majority of classification decisions automatically. And that is exactly what rule-based entity classification does. Instead of a human making each decision one at a time, software applies a set of classification rules to every entity in the drawing simultaneously.
How LayerGuard Handles the Layer 0 Problem
This is the exact problem that LayerGuard was built to solve. Its Repair mode is designed specifically for drawings where everything has been dumped onto Layer 0 or a handful of non-standard layers.
Here is what happens when you run Repair mode on a Layer 0 drawing. LayerGuard examines every entity in the drawing and classifies it based on its entity type and properties. DIMENSION entities go to LG_DIMS. TEXT and MTEXT go to LG_TEXT. HATCH entities go to LG_HATCH. LEADER and MULTILEADER entities go to LG_DIMS. And so on through a set of nine canonical layers that cover the standard categories needed for manufacturing drawings:
- LG_CUT — Primary cut/contour geometry
- LG_DIMS — Dimensions and leaders
- LG_TEXT — Text and annotations
- LG_HATCH — Hatch patterns and fills
- LG_CONSTRUCTION — Construction and reference geometry
- LG_CENTERLINE — Centerlines and center marks
- LG_BEND — Bend lines for sheet metal
- LG_BORDER — Title block and border elements
- LG_OTHER — Everything that does not fit the above
The result is a drawing that went from "everything on Layer 0" to a properly organized structure in seconds. Not 45 minutes. Not an hour. Seconds.
Is it perfect every time? No. Some ambiguous geometry might end up on LG_OTHER and need a quick manual check. But the 90% of entities that can be classified by rule are handled automatically, and the remaining 10% is a lot easier to deal with when it is isolated on its own layer instead of buried in a pile of 500 other entities.
What I particularly appreciate about the way LayerGuard approaches this is that it does not try to guess what your company standard is. It uses its own LG_* prefix so you always know which layers were created by the tool versus which layers already existed in the drawing. If your shop uses different layer names, you can remap them after the fact, but at least the classification work is done.
Preventing the Problem in the First Place
Fixing Layer 0 drawings is necessary, but it is worth spending a minute on prevention too.
Ask Vendors for DWG Files, Not PDFs
Whenever possible, get the native DWG. A PDF will always lose layer information. If the vendor is concerned about sharing their proprietary drawing, ask them to at least maintain layers in the export. Some vendors will send a DWG with layers if you ask; they just default to PDF because nobody asked for anything different.
Provide Your Layer Standard to Vendors
If you have a layer standard (and you should), send it to your vendors along with the purchase order. A simple document or DWT template file that says "put cut geometry on CUT, dimensions on DIMS" costs nothing to share and can save hours of cleanup on the receiving end.
Check Files on Receipt
Build a quick check into your receiving workflow. Before a drawing goes into the queue for programming, someone spends 30 seconds opening it and checking the layer structure. If everything is on Layer 0, it gets flagged for cleanup before it reaches the shop floor. This is where LayerGuard's AuditOnly mode is useful—it can scan a drawing and report layer issues without modifying anything, giving you a go/no-go decision in seconds.
The Bigger Picture
The Layer 0 problem is really a symptom of a larger issue: the CAD world does not have a universal standard for how drawings should be organized. Every company has their own layer naming convention, their own color assignments, their own rules about what goes where. And when drawings move between companies, those differences create friction.
You cannot control how your vendors set up their drawings. You cannot control what software they use or how they export files. What you can control is how you handle those files when they arrive. Having a reliable, repeatable process for normalizing incoming drawings—whether that is a manual checklist or an automated tool—is the difference between a shop that spends its mornings fixing drawings and a shop that spends its mornings making parts.
Stop spending your mornings sorting someone else’s mess. Set up a standard, enforce it consistently, and automate the cleanup wherever you can. Your future self will thank you—and so will the people running your machines.