Batch Publish AutoCAD Drawings to PDF with Claude Code

Batch publishing AutoCAD drawings to PDF starts with choosing exactly which layouts belong in the delivery. Across several DWGs, a misplaced sheet, inconsistent page setup or missing reference can leave you rebuilding the package just before an issue deadline.

Claude Code can help prepare a sheet manifest, write a publishing script and check the resulting logs. AutoCAD handles the drawing interpretation and PDF output through its Publish workflow. You approve the layouts and plotting settings, then review the saved PDF before delivery.

This guide follows three DWG files containing six paper-space layouts. You will save an AutoCAD publish list, use Claude Code to prepare a repeatable job, and check that the final PDF contains all six sheets in the intended order.

The steps below use AutoCAD and Claude Code together on a Vagon Windows computer.

Prepare AutoCAD and Claude Code on a Vagon Windows Computer

For recurring drawing issues, prepare a Vagon Windows workspace with AutoCAD, Claude Code and one complete project copy, then start by previewing its first sheet. The publishing batch uses the cloud computer’s resources while your everyday computer stays available. Return to the same desktop to adjust plotting settings and inspect the finished PDF.

Start with full AutoCAD for Windows, activated through your Autodesk account with the appropriate license. This guide uses AutoCAD 2026 documentation as its reference. Open AutoCAD once and complete any first-run prompts before trying to automate a publishing command.

Install Claude Code inside the same Windows computer using Anthropic’s native Windows setup instructions, then sign in with your Claude Code access. Keep this workflow in native Windows so the assistant and AutoCAD use the same project paths.

Create the project folder C:\VagonProjects\Office-Issue. Keep its contents organized as follows:

• drawings: working copies of the three DWGs and their referenced files, preserving relative paths.

• jobs: the DSD publish list and SCR script you will create.

• reports: the sheet manifest and archived publishing logs.

• output: a separate subfolder for each issue’s PDF.

Bring the project’s required Xrefs and images, and make its fonts, plot styles and plotter configurations available to AutoCAD. Open the copied drawings and resolve missing-reference warnings before proceeding. Keep the original project separately so publishing adjustments stay within the working copy.

In PowerShell on the Vagon computer, verify Claude Code and start it from the project folder:

claude --version
cd C:\VagonProjects\Office-Issue
claude

claude --version
cd C:\VagonProjects\Office-Issue
claude

claude --version
cd C:\VagonProjects\Office-Issue
claude

You can now ask Claude Code to work with the project’s text files and scripts. In AutoCAD, open the first drawing and confirm that its intended layouts are available. Keep the cloud computer running throughout the publishing job; inspect the first sheet before expanding to the complete set.

Define the Six Sheets and Their PDF Page Order

Use one manifest row for each layout you intend to publish. A DWG can contain several layouts, including working sheets that do not belong in the current issue. Selecting three drawing files therefore does not establish which six pages should appear in the PDF.

For this example, use the following mapping. Drawing paths are relative to C:\VagonProjects\Office-Issue; the layout names must match the names in the copied DWGs.

Ask Claude Code to save this mapping as reports/sheets.csv, using the columns page, sheet_id, drawing_path and layout_name. Have it check that page numbers run from 1 through 6, sheet IDs are unique, no drawing/layout pair is repeated, and every referenced DWG exists. Resolve relative paths against the project folder rather than the location of the CSV.

Then confirm the layout names in AutoCAD. File existence checks cannot establish which layouts a DWG contains. If your actual names differ from the example, update the manifest with those exact names before constructing the publish list. Keep the Sheet ID column tied to the drawing’s title block, even when its layout tab uses a different naming convention.

Source: Autodesk AutoCAD Blog

Exclude the Model tab and any superseded or working layouts from this issue. When you build the Publish list, compare its entries against the manifest and arrange them by the explicit PDF page number. Filename sorting is not the delivery order.

The target is now precise: one six-page A3 landscape PDF, with A-101 first and A-502 last. The manifest records that requirement; the DSD you save in AutoCAD will control the actual publishing operation.

Approve the Page Setup Before Automating the Batch

Open office-plans.dwg and select the A-101 layout. Use it to establish the publishing settings for this example before applying them to the remaining sheets. If your office already has an approved plotting setup, start there and check that it matches the intended delivery.

In the Output tab, open Page Setup Manager and create a named page setup called ISSUE_A3_PDF. You can also import a suitable setup from an existing drawing. Give the setup a stable name so you can recognize it when assigning settings in the Publish list.

Source: Autodesk Help

Configure these choices for the six-sheet example:

• Printer/plotter: an installed Autodesk PDF PC3 configuration, available on the Vagon computer.

• Paper: A3, 420 × 297 mm, with landscape orientation. Check the printable margins for the selected device.

• Plot area: Layout, using the existing paper-space sheet arrangement.

• Plot styles: the project’s approved CTB or STB, with Plot with Plot Styles enabled where required by that standard.

• Lineweights: settings that preserve the project’s intended printed line hierarchy.

AutoCAD plots a Layout plot area at 1:1. This is the paper-space output scale. A floor-plan viewport might separately display model geometry at 1:100, while a detail viewport uses 1:10. Keep those viewport scales intact; changing the sheet’s plotting setup should not become an unrequested drawing-scale adjustment.

Source: Autodesk Help

Use the plot preview to inspect the title block, sheet border, annotations and fine linework. Look for content outside the printable area, unexpected colors and text that no longer fits its intended space. Check transparency settings if the drawing relies on transparent objects.

Resolve missing-font or reference warnings in the working project before accepting the setup. A substituted font can change the appearance of a note even when the PDF export itself completes.

Repeat the settings check for the other five layouts, applying or importing ISSUE_A3_PDF as appropriate, and save the working DWGs. Preview at least one elevation and one detail as well as the plan: their different content can expose problems the first sheet does not reveal. Once the sheet settings are approved, assemble the complete Publish list.

Save and Test an AutoCAD Publish List

Enter PUBLISH in AutoCAD to open the Publish dialog. Clear unwanted entries already loaded from open drawings, then use Add Sheets to select the three working DWGs. Remove Model entries and any layouts absent from reports/sheets.csv.

Source: Autodesk AutoCAD Blog

Arrange the remaining six entries in manifest order, from A-101 through A-502. AutoCAD initially combines the drawing and layout names in its Sheet Name column, so an entry such as office-plans-A-101 is expected. Compare its source drawing and layout with the manifest rather than assuming the displayed name must equal the sheet ID.

Check each row’s Page Setup selection. Use ISSUE_A3_PDF, importing it from the prepared drawing where necessary. Resolve any sheet-status warnings before continuing. Select PDF under Publish To and review the PDF preset so it matches your approved delivery settings.

Source: Autodesk AutoCAD Blog

Create output/pilot inside the project folder. In PDF Publish Options, configure the first complete test package:

• Set Location to C:\VagonProjects\Office-Issue\output\pilot.

• Enable Multi-sheet file to combine the six layouts.

• Clear Prompt for name and set File name to office-issue.pdf.

• Choose the required vector and raster quality, plus any layer information or bookmarks needed by the recipient.

Keep these choices explicit. Six separate PDFs and one six-page PDF are different delivery packages, even when they contain the same drawings. Avoid adding optional PDF data solely because the controls are available; use the recipient’s requirements.

Source: Autodesk AutoCAD Blog

Use Save Sheet List to save C:\VagonProjects\Office-Issue\jobs\office-issue.dsd. Before relying on it, reload the saved list, replacing existing entries rather than appending them, and confirm the sheet order, page setups and output options. This checks the artifact you will pass to the script.

Before the pilot, open Options > Plot and Publish. Under the logging options, enable Automatically Save Plot and Publish Log and select Save One Log File Per Plot. In Options > Files, locate the configured plot-and-publish log location and record its full path.

Source: Autodesk Help

For this pilot, clear Publish in Background so you can follow the operation in the current session. Click Publish and wait for completion. Identify the newly written job log by its timestamps and drawing/layout records, and confirm it contains the information needed for the later comparison. Open output/pilot/office-issue.pdf and inspect all six pages against the manifest, including their title blocks and orientation.

If the pilot has missing sheets, clipping or incorrect plotting, correct the working setup and repeat it. Once the complete package is acceptable, retain the DSD as the basis for scripted publishing.

Ask Claude Code to Build a Repeatable Publish Job

Keep the reviewed pilot intact. Create output/run-001, load jobs/office-issue.dsd in AutoCAD, and change the PDF output location to that new folder. Keep office-issue.pdf as the filename, save the DSD again, and confirm the settings after reloading it. The script will use this saved publishing configuration.

In the Claude Code session opened at the project root, give the assistant a bounded task:

Prepare a publish job for this project.
Read reports/sheets.csv and check its six ordered rows, unique sheet IDs,
unique drawing/layout pairs, and existing DWG paths relative to this folder.
Confirm jobs/office-issue.dsd exists. Do not modify the DWGs or DSD.
Create jobs/office-issue.scr to run AutoCAD's -PUBLISH command with the
absolute DSD path. Use ASCII text, quote the path, and end with a blank line.
Report any failed checks before proceeding. Do not infer layout existence
from file checks or claim that publishing has completed.
Show me the script before any application launch

Prepare a publish job for this project.
Read reports/sheets.csv and check its six ordered rows, unique sheet IDs,
unique drawing/layout pairs, and existing DWG paths relative to this folder.
Confirm jobs/office-issue.dsd exists. Do not modify the DWGs or DSD.
Create jobs/office-issue.scr to run AutoCAD's -PUBLISH command with the
absolute DSD path. Use ASCII text, quote the path, and end with a blank line.
Report any failed checks before proceeding. Do not infer layout existence
from file checks or claim that publishing has completed.
Show me the script before any application launch

Prepare a publish job for this project.
Read reports/sheets.csv and check its six ordered rows, unique sheet IDs,
unique drawing/layout pairs, and existing DWG paths relative to this folder.
Confirm jobs/office-issue.dsd exists. Do not modify the DWGs or DSD.
Create jobs/office-issue.scr to run AutoCAD's -PUBLISH command with the
absolute DSD path. Use ASCII text, quote the path, and end with a blank line.
Report any failed checks before proceeding. Do not infer layout existence
from file checks or claim that publishing has completed.
Show me the script before any application launch

Review the checks and generated file. The publishing portion should be this small:

_-PUBLISH
"C:\VagonProjects\Office-Issue\jobs\office-issue.dsd"

_-PUBLISH
"C:\VagonProjects\Office-Issue\jobs\office-issue.dsd"

_-PUBLISH
"C:\VagonProjects\Office-Issue\jobs\office-issue.dsd"

The first line invokes the command-line publisher; the second answers its sheet-list prompt. The underscore requests the global command name. Preserve the final blank line in the actual file. AutoCAD’s command script rules make whitespace significant, so avoid adding explanatory text outside semicolon-prefixed comment lines.

Source: Autodesk Help

Before running it, archive the pilot’s identified job log. The -PUBLISH command also documents a CSV named from the DSD, with an existing file overwritten on the next run. After the first scripted publish, locate that generated CSV and compare it with any separate log produced by the configured logging options. Retain both if they differ; identify the relevant job from their contents rather than assuming the files share a location or schema.

For the first scripted run, return to AutoCAD, cancel any active command, enter SCRIPT, and select jobs/office-issue.scr. Check this minimal sequence against your installed release’s prompts before using it for subsequent issues. Publishing from an SCR runs in the foreground regardless of BACKGROUNDPLOT, so let the command finish before interacting with the drawing.

Source: Autodesk Help

Once that route works, Claude Code can also launch AutoCAD through its shell using the documented startup script switch. For a standard AutoCAD 2026 installation, the PowerShell invocation is:

& "C:\Program Files\Autodesk\AutoCAD 2026\acad.exe" "C:\VagonProjects\Office-Issue\drawings\office-plans.dwg" /b "C:\VagonProjects\Office-Issue\jobs\office-issue.scr"

& "C:\Program Files\Autodesk\AutoCAD 2026\acad.exe" "C:\VagonProjects\Office-Issue\drawings\office-plans.dwg" /b "C:\VagonProjects\Office-Issue\jobs\office-issue.scr"

& "C:\Program Files\Autodesk\AutoCAD 2026\acad.exe" "C:\VagonProjects\Office-Issue\drawings\office-plans.dwg" /b "C:\VagonProjects\Office-Issue\jobs\office-issue.scr"

Confirm the executable path first. Use this as an alternative startup route, with the working drawing closed in other AutoCAD sessions, and watch for startup prompts. The command does not include an automatic quit or save operation.

An application launch establishes only that the job was started. Wait for AutoCAD’s publishing result, then check output/run-001/office-issue.pdf and the new publish log before reporting success.

Check the Publish Log and the Saved PDF

After AutoCAD finishes, inspect the current job’s Plot and Publish Details and locate its new CSV log. Check that the recorded start and completion times belong to run-001. A log from the pilot cannot establish what happened during the scripted run.

Source: Autodesk Help

Create reports/run-001 and copy the identified sheet-level job log there as office-issue.csv before another publishing attempt can overwrite it. This is your archive location, not an AutoCAD default output path. If the DSD-named CSV and configured job log are separate files, retain the additional file under a distinct name. Keep reports/sheets.csv unchanged as the intended sheet list.

Give Claude Code this follow-up task:

Compare reports/sheets.csv with reports/run-001/office-issue.csv.
Inspect the CSV structure before interpreting it. Identify this run’s job
and sheet records; resolve manifest paths against the project root.
Write reports/run-001/validation.md with expected and matched sheet counts,
missing or duplicate drawing/layout pairs, and raw failure/warning statuses.
For output/run-001/office-issue.pdf, inspect available PDF tools and report
page count and page dimensions only if a suitable tool actually checks them.
Record tool names, input paths, timestamps and any fields you cannot verify.
Keep unknowns explicit. List visual checks as awaiting reviewer approval.
Do not modify the source files or declare the package approved for issue

Compare reports/sheets.csv with reports/run-001/office-issue.csv.
Inspect the CSV structure before interpreting it. Identify this run’s job
and sheet records; resolve manifest paths against the project root.
Write reports/run-001/validation.md with expected and matched sheet counts,
missing or duplicate drawing/layout pairs, and raw failure/warning statuses.
For output/run-001/office-issue.pdf, inspect available PDF tools and report
page count and page dimensions only if a suitable tool actually checks them.
Record tool names, input paths, timestamps and any fields you cannot verify.
Keep unknowns explicit. List visual checks as awaiting reviewer approval.
Do not modify the source files or declare the package approved for issue

Compare reports/sheets.csv with reports/run-001/office-issue.csv.
Inspect the CSV structure before interpreting it. Identify this run’s job
and sheet records; resolve manifest paths against the project root.
Write reports/run-001/validation.md with expected and matched sheet counts,
missing or duplicate drawing/layout pairs, and raw failure/warning statuses.
For output/run-001/office-issue.pdf, inspect available PDF tools and report
page count and page dimensions only if a suitable tool actually checks them.
Record tool names, input paths, timestamps and any fields you cannot verify.
Keep unknowns explicit. List visual checks as awaiting reviewer approval.
Do not modify the source files or declare the package approved for issue

Count sheet records rather than assuming every CSV row represents a published page. If the archived log lacks a required field, have Claude flag that gap and consult the additional log or AutoCAD’s job details. A missing status is not a successful status.

Next, open output/run-001/office-issue.pdf in a PDF viewer and check the delivered artifact:

• Completeness: exactly six pages, with no blank replacement pages or duplicated sheets.

• Order: A-101, A-102, A-201, A-202, A-501 and A-502, confirmed against the visible title blocks.

• Paper: A3 landscape on every page, using the viewer’s page-size information rather than the apparent size on screen.

• Appearance: readable notes, correct lineweight hierarchy, complete borders and visible referenced content.

• Revision: the intended issue information appears on every sheet that requires it.

Claude Code can help check page count and dimensions if a suitable PDF inspection tool is installed. Require it to name the tool and report what it actually checked. A six-page count cannot establish that those are the correct six sheets, and extracted text alone cannot confirm that fine linework remains legible.

For a scale-sensitive delivery, check a known distance using a calibrated PDF measurement tool or a correctly configured actual-size print. Match the check to that viewport’s stated scale. Zooming a page to fill the screen does not establish printed scale.

After reviewing the PDF, add your name and review date to reports/run-001/validation.md and resolve or document the outstanding items. Keep failed automated checks separate from items still awaiting visual review. Release the package only after both the publishing evidence and the saved PDF support the intended delivery.

Repeat the Issue Without Reusing Stale Results

Before preparing the next revision, copy the manifest, DSD and SCR used for run-001 into reports/run-001. Keep them with its archived log and validation record. This preserves the publishing instructions associated with the reviewed PDF even when you later update the working files in jobs.

For the next attempt, create output/run-002 and a matching reports/run-002 folder. Use a new run number for a retry as well as a new drawing revision, so an unsuccessful export remains distinguishable from its replacement.

Update the working manifest only if the delivery’s sheet selection or order has changed. Ask Claude Code to compare it with the archived version and summarize additions, removals and reordered sheets. Confirm renamed or replacement layouts in AutoCAD before updating the Publish list.

Load the DSD in AutoCAD, review the selected sheets, and change the PDF destination to output/run-002. Save and reload the DSD to confirm that destination before invoking the same SCR. Recheck any changed Xrefs, fonts or plotting resources; retaining a page setup name does not establish that its dependencies are unchanged.

If a sheet fails, retain the failed run’s evidence and identify the affected drawing/layout pair. Correct the specific source or plotting problem in the working copy, preview that sheet, then republish the complete six-sheet package into a fresh run folder. This keeps the final combined PDF and its publish log associated with one complete attempt.

Avoid silently omitting a failed sheet or replacing the accepted PDF with a partial result. If the delivery scope changes, record that decision in the manifest and repeat the acceptance checks against the new scope.

The reusable workflow is now the manifest, AutoCAD-generated DSD, short SCR and per-run verification record. Together, they let you repeat an issue while retaining a clear account of what was selected, published and approved.

FAQs

Can Claude Code convert DWG files to PDF without AutoCAD?

This workflow requires AutoCAD to interpret the drawings and generate the PDF. Claude Code prepares text files, invokes the available application workflow and helps inspect its outputs. Asking it to write a script does not supply a CAD publishing engine. A different converter would need its own compatibility and output-quality checks.

Do I need an AutoCAD MCP server for batch publishing?

No. The DSD and SCR route uses AutoCAD’s documented command-line publishing mechanism. You can run the script manually inside AutoCAD, or use the startup invocation after checking it in your environment. MCP becomes relevant if you separately need supported tools for inspecting or controlling a live drawing session.

Can I create one PDF per layout instead of a combined document?

Yes. Clear Multi-sheet file in PDF Publish Options to produce separate sheet PDFs. Treat this as a different output contract: confirm the generated filenames, check that every manifest entry has a corresponding file, and inspect each file’s page count. Save the revised publishing configuration before reusing it.

Will the same script work in AutoCAD LT or AutoCAD for Mac?

This guide targets full AutoCAD on Windows. Do not carry its executable path or PowerShell invocation into another edition or operating system unchanged. Check that product’s publishing commands, script support, PDF options and startup behavior, then repeat the pilot. A DSD created for one environment still needs valid drawing paths and available plotting resources in the destination environment.