Guide
Can Claude Read DWG Files? DXF & AutoCAD MCP Explained
Can Claude read DWG files? Compare direct upload, PDF review, DXF extraction and AutoCAD MCP, then build your Claude CAD workspace on Vagon Cloud Computer.

Claude can help you understand a DWG drawing, but the route matters. DWG is not listed among Claude’s supported upload formats, so attaching an AutoCAD file is not a documented way to give it native access to the drawing’s contents.
Start with the question you need answered. A PDF or image can support a discussion about the visible sheet. A DXF export, processed into structured data, can expose layers, entity types and block attributes. A compatible AutoCAD MCP connector lets Claude query information from the open drawing through tools.
This guide helps you choose the right route and check the answer. For ongoing CAD work, it also shows how to put Claude, AutoCAD and the connector in a Vagon workspace while keeping your own computer available for other tasks.
Can You Upload a DWG Directly to Claude?
DWG and DXF are absent from Anthropic’s standard document upload list. A DXF export therefore still needs a suitable reader or text/data extraction step before Claude can use its contents reliably.
The distinction is between giving Claude information and giving it a way to retrieve information. Uploading a CSV of layer names supplies that exported list. Connecting Claude to a drawing reader lets it request data through the reader’s available tools. The completeness of the answer depends on what the export contains or what the tool exposes.
Choose the route around the question:
What you want to know | What to provide or connect | What the answer is based on |
|---|---|---|
What does this sheet show? | A readable PDF or image | Visible geometry, labels and annotations |
Which layers and entity types are in the drawing? | A scoped JSON/CSV report extracted from DXF | Fields included in the extraction |
What is in the active AutoCAD document? | A compatible AutoCAD MCP connector | Drawing data returned by its tools |
Can I inspect the DWG without a live AutoCAD session? | A compatible DWG parser or parser-backed MCP server | Objects supported by that reader |
Claude Code changes how you can access those routes. It can use configured MCP tools and run permitted commands in its working environment. A file path alone does not supply a DWG decoder; the required software must still be available.
For our example, office-plan-review.dwg, explaining room labels and counting model-space entities are separate requests. Decide which result you need before preparing the file. That choice determines whether to export a sheet, extract drawing data or connect to AutoCAD.
Use a PDF or Image When You Need to Understand the Sheet
If you want Claude to explain a floor plan, summarize drawing notes or help locate a detail, start with a readable plot. This route gives you a useful first discussion without installing a CAD connector. It works best when the question can be answered from what someone could see on the sheet.

Source: Autodesk
For office-plan-review.dwg, plot the relevant layout to office-plan-review.pdf. Open the PDF yourself before uploading it: check that the intended layers appear, the sheet is not clipped, and room names and dimensions remain legible when enlarged. Include the legend or title block when it explains symbols, units or the drawing revision.

Source: Autodesk
A PNG or JPEG is useful for a focused detail. Supply an overview as well if the crop would otherwise lose its location. When text is too small, provide a closer view rather than asking Claude to reconstruct unreadable characters. Anthropic’s current PDF processing guidance limits visual analysis to PDFs of 100 pages or fewer; files with 101–1000 pages receive text processing only. Extract the relevant sheets into a smaller PDF when you need Claude to examine drawing geometry and annotations.
Make the first request specific:
Review the attached office-plan-review.pdf. Summarize the room labels and general arrangement shown on page 1. List the visible drawing notes separately. Identify anything you cannot read, and refer to the page and room label when describing a finding. Do not infer missing dimensions.
Compare the response with the sheet, especially where a symbol, overlapping annotation or faint line could change the interpretation. Ask Claude to distinguish a printed dimension from an estimate based on appearance.
A plotted sheet does not reliably reveal native layer assignments, object handles or block attributes. Even a vector PDF should not be treated as the original CAD database. If your next question concerns those properties, move to a structured export or drawing connection instead of requesting a more confident visual answer.
Use DXF and Structured Exports for Layers, Entities and Attributes
Choose this route when you need an inventory you can sort, filter or compare. For office-plan-review.dwg, the useful result might be a list of layers, counts of entity types and the attribute values attached to selected block references. You can give Claude that data without connecting it to a live AutoCAD session.
Export a Real DXF Copy
Open the drawing in AutoCAD and use Save As with DXF output to create office-plan-review.dxf. Record the selected format version and whether you exported the whole drawing or selected objects. Keep the original DWG separately. If someone else supplies the file, ask them for a DXF export from the source drawing.
DXF can be ASCII or binary. ASCII DXF contains text that you can inspect, but it is still structured drawing data rather than a plain-language description. A small excerpt saved as TXT can help explain a particular record; it is a poor basis for counting everything in a large drawing. Renaming a binary DWG to .txt does not perform a conversion.

Source: Autodesk
Extract the Fields Your Question Needs
A Python library such as ezdxf can read DXF data for an extraction script. It does not replace the DWG-to-DXF conversion step. With Claude Code, you can ask the assistant to prepare and run that script in an environment containing Python and the library. In a standard chat, have the extraction run separately and upload its JSON or CSV output.
Define the report before requesting the script:
Source: DXF filename, the format version reported in the file and extraction time. Keep any separately supplied export history alongside these fields.
Scope: model space, paper-space layouts or a named selection, with exclusions stated.
Inventory: layer-table entries and entity counts grouped by layer and type, kept separate so zero-count layers remain visible.
Block data: reference handle, block name and requested attribute tags and values, where available.

Source: Autodesk
The ezdxf layout and query documentation distinguishes model space, paper space and block definitions. Keep that distinction in the report: counting top-level model-space entities does not count all geometry nested inside blocks. Read attached block attributes explicitly rather than treating visible text as an attribute value.

Source: Autodesk
For an execution-capable Claude Code session, a bounded request could be:
Read office-plan-review.dxf using Python and ezdxf. Save reports/drawing-review.json containing the source filename, DXF format version reported in the file, extraction time in UTC, declared units, all layer-table names and top-level model-space entity counts grouped by layer and type. Keep any supplied export-history notes separate; do not infer the exporting application or its version from the DXF format version. Separately list attached attribute tags and values for top-level block references. Do not traverse nested blocks or external reference files. State these exclusions, report extraction errors, and leave the source unchanged. If a dependency is missing or the report already exists, report it before proceeding.
Review the extraction log before asking Claude to summarize the report. Treat units as a declared setting to verify against a known dimension. Flag unavailable properties and unsupported content instead of filling gaps with guesses. The resulting analysis applies to this export and its stated scope; changes made later in AutoCAD require a fresh extraction.

Source: Autodesk
Use AutoCAD MCP When Claude Needs the Open Drawing
Use a live connection when your questions depend on the drawing you are currently working in. You might inspect a layer, make a manual correction in AutoCAD, then ask Claude to query the updated state. That avoids generating another DXF export for each exchange.
The connection follows this path: Claude Code → MCP connector → AutoCAD → drawing data returned to Claude. MCP provides the tool connection; the connector determines which AutoCAD operations are available. Claude does not gain every application capability simply because a server connects successfully.
Choose a Connector That Supports Your Client
One documented option is the third-party AUTOM8LABS MCP Connector for AutoCAD. Its current documentation lists Claude Code and Claude Desktop, full AutoCAD 2022–2027 on 64-bit Windows 10 or 11, and a local stdio bridge. AutoCAD LT is excluded for this connector. The vendor offers a free read-only inspection tier; paid connector features, AutoCAD licensing and Claude access are separate. Check the requirements against your installation before configuring the connection.

Source: AUTOM8LABS
For the full installation sequence, follow our AutoCAD with Claude Code guide. Keep the assistant, bridge and AutoCAD in the same Windows environment for this workflow. A successful connection is the starting point; confirm which tools it actually offers before requesting drawing analysis.
Start With a Read-Only Drawing Inventory
Open a working copy of office-plan-review.dwg. Enable the connector’s read-only session option and reconnect the client so its available tools refresh. AUTOM8LABS documents tools including get_drawing_info, list_layers and get_entities; names and capabilities differ across other servers.
Begin by asking Claude to identify the active drawing and its path. If several documents are open, resolve that identity before querying their contents. Then request a bounded inspection:
Inspect the active office-plan-review.dwg through the connected AutoCAD tools. Confirm the drawing path and declared units first. List the layers and report top-level model-space entity counts grouped by layer and type. State whether nested blocks and external references are excluded. Retrieve attached attributes for top-level block references only if the available tools support it. Do not modify or save the drawing. Use your file tools to save reports/drawing-review-live.json with the returned inventory, source path, inspection time in UTC, query scope, limitations and reported unsaved-change state. Mark unavailable metadata as unknown. If the report already exists, stop before overwriting it.
Ask for the underlying query results alongside the summary. If a query returns records in pages, have Claude retrieve the remaining pages or explicitly label the result as partial. A count derived from one response page must not become a claimed total for the drawing.
Keep this inventory comparable with the DXF report: use the same space, grouping and exclusions. Differences can then be investigated as changes in the drawing, extraction scope or tool coverage. Once the inspection is useful, decide separately whether to authorize a specific edit. Reading a drawing is not permission to clean up its layers or change geometry.
Distinguish Live AutoCAD From a DWG Parser
A server with “DWG” or “AutoCAD” in its name may use a different architecture. For example, the community DWG MCP Server documents LibreDWG-backed file queries and rendering without a live AutoCAD session. It keeps source files read-only; supported property changes occur in memory and are discarded when the document closes.
That can serve file-inspection questions, but it does not establish access to your active AutoCAD document or the ability to save an edited DWG. Choose according to the required result and the reader’s supported objects.
If your chosen client supports computer use, reserve interface interaction for a step that needs it, such as inspecting a dialog or navigating the viewport. For exact layer membership or entity counts, prefer the relevant structured query. A screenshot can complement those results without replacing them.
Give Claude and AutoCAD Their Own Vagon Workspace
Give your CAD assistant a workspace where it can do the job while you keep using your own computer. With Claude Code on Vagon, you can prepare a Windows cloud desktop for AutoCAD, the MCP connector and your project files, then access that desktop through your browser.
That separation is useful even if you already own a capable workstation. Drawing inspection, DXF extraction and follow-up CAD work can run on the cloud computer while you use your laptop for another project or a meeting. For workflows that also use supported computer-use tools, the application interaction belongs on that separate desktop rather than among your personal windows.
The practical advantage continues when you need to intervene. Open AutoCAD in the same workspace, inspect the objects behind Claude’s report and make a manual correction there. You can then ask for another query against the updated drawing. The report, source application and next action stay together, reducing the need to move the project back to your local computer just to investigate a finding.
Start with the drawing inventory from this guide:
Create a Windows workspace. Use Windows for the live AutoCAD connector described above, and choose resources around your drawing workload.
Prepare the working tools. Set up AutoCAD, Claude Code and the compatible MCP bridge inside that desktop. Sign in with your Claude account and activate the required software licenses.
Bring over one project copy. Transfer
office-plan-review.dwgwith the references it needs, then open it in the cloud AutoCAD session.Run the first inspection. Confirm the active document, enable the connector’s read-only mode and request the scoped layer and entity inventory. Review the returned data alongside the drawing.
As your projects grow, Vagon’s selectable performance configurations let you adjust the machine while retaining your files.
Create your Claude workspace on Vagon and run your first drawing inventory.
Check the Drawing Data Before Acting on Claude’s Answer
Turn the inventory into something you can trace back to the drawing. Keep reports/drawing-review.json as the DXF export snapshot and reports/drawing-review-live.json as the live-session report. Their source identity, scope and timestamps should show which drawing state each analysis describes.
Before accepting a finding, check:
Drawing identity: Does the reported path match the project copy you intended to inspect? Confirm the revision and whether unsaved changes were present during the live query.
Units and dimensions: Compare the declared units with a known length in the drawing. Distinguish measured geometry from displayed dimension text, particularly where text overrides may be involved.
Counting scope: Compare one layer’s reported count with an independent selection or query in AutoCAD using the same space and entity types. Investigate differences before extending the conclusion to the whole drawing.
Block attributes: Check a sampled reference’s handle, block name and tag/value pairs against its properties in AutoCAD. Confirm that the report refers to the intended insertion.
Missing content: Record unresolved references, unsupported objects and incomplete query pages. An excluded object is not evidence that the drawing contains none.

Source: Autodesk
Ask Claude to revise the summary when these checks uncover a mismatch, keeping the corrected scope beside the finding. Preserve the query results so another reviewer can follow the reasoning.
If you later approve an edit, save it to a separate DWG and reopen that file in AutoCAD. Check the changed objects and regenerate the relevant report. That completes the handoff from an assistant’s explanation to a drawing you can continue working with.
FAQs
Can Claude inspect a DWG without AutoCAD installed?
Yes, through a compatible external reader. A parser-backed tool such as the community DWG MCP Server documents this route. Its supported objects and properties determine what Claude can inspect. Alternatively, ask the sender for a PDF or structured export. Neither approach requires Claude to decode the DWG natively.
Does renaming DWG or DXF to TXT make it readable?
Renaming a DWG does not convert its binary contents into text. An ASCII DXF is already text-based, so a copy supplied as TXT can expose its records for discussion. That changes how you present the content, not the format’s complexity or the reliability of a whole-drawing analysis. A binary DXF still needs appropriate software.
Does reading a DWG through MCP mean Claude can save edits?
No. Inspection, modification and saving are separate capabilities. A live AutoCAD connector may expose editing tools, depending on its configuration and edition. A parser may allow only queries or temporary in-memory changes. Check the specific tool’s documentation and permissions before requesting a saved DWG as the deliverable.
What should I send when a drawing is too large or contains unsupported objects?
Narrow the request to a named layout, region, layer or object set. For visual questions, provide readable sheet extracts with enough context to identify their location. For data questions, request filtered results and complete pagination. If the reader cannot interpret a custom object, ask for a report from the originating application and retain that limitation in the summary.

Written by
Mert Boz
Mert is a philosophy student with a strong interest in economics, motorsports, and basketball. He enjoys thinking about how the world works, both in theory and in real life. In his free time, you can often find him watching a race, following a basketball game, or reading about economic ideas.
More posts by this writer →
Related
More on Architecture & Visualization
All posts →






