You attempt to import a multi-page PDF into AutoCAD using PDFIMPORT, but AutoCAD only allows one page to be processed at a time. Every sheet requires relaunching the command, selecting another page, and repeating the same workflow manually.

On large drawing sets, users typically encounter:

• AutoCAD freezing during import
• excessive DWG file growth
• imported geometry spread across dozens of layers
• overlapping pages after conversion
• missing or corrupted text objects

This affects:

• AutoCAD
• AutoCAD LT
• Civil 3D
• AutoCAD-based vertical products

The Root Cause (The “Why”)

The limitation comes from the way AutoCAD processes PDF geometry internally.

The PDFIMPORT engine converts:

• vectors
• splines
• hatches
• SHX text
• TrueType fonts
• layer structures

into live DWG entities during the import operation.

AutoCAD’s native import workflow only processes one PDF page per import instance. Autodesk designed the dialog this way to reduce:

• memory spikes
• font reconstruction conflicts
• geometry corruption
• unstable layer recreation

This is not a software bug. It is a limitation of the PDF conversion workflow itself.

Performance problems become significantly worse when:

• PDFs contain dense hatch data
• consultant exports include hundreds of embedded layers
• raster and vector objects are mixed together
• unsupported fonts trigger substitution routines
• users import entire page sets as geometry instead of using underlays

Another major factor is the PDFSHX system variable.

When:

PDFSHX = 1

AutoCAD attempts to recognize exploded PDF text and reconstruct SHX text objects from linework. On complex PDFs, this increases:

• import time
• memory usage
• conversion failures
• DWG size

For large imports, disabling SHX recognition improves stability dramatically.

The Solution — The Fastest “Underlay-First” Workflow

The fastest professional workflow is:

1. attach all required pages as underlays first
2. convert only the pages that actually require editing

This bypasses the repetitive single-page limitation inside the standard PDFIMPORT dialog.

Step 1 — Attach the PDF as an Underlay

Type:

PDFATTACH

or open the:

External References Palette

Select the multi-page PDF file.

Step 2 — Select Multiple Pages

Inside the Attach PDF Underlay dialog:

• use Ctrl + Click
• or Shift + Click

to select multiple pages simultaneously.

Important Technical Note

Selecting multiple pages does not place them automatically.

AutoCAD still requires one placement click per selected page.

Example:

• select 10 pages
• click 10 times inside the drawing area

This is where many users assume AutoCAD has frozen.

Step 3 — Place the Underlays Properly

Enable:

Specify On-Screen

Then place each page individually.

Best practice:

• place pages sequentially from left to right
• avoid stacking pages on top of each other
• temporarily place large page sets outside the active work area

Notes:

• preview thumbnails may appear delayed
• large PDFs may pause between placements
• each page becomes an independent PDF underlay reference

Step 4 — Convert Only the Required Pages

Select a single underlay page.

On the contextual ribbon tab, click:

Import as Objects

This launches the PDFIMPORT engine.

Important Warning

Do not blindly type:

ALL

during selection prompts if multiple PDF underlays exist in the drawing.

Why:

• AutoCAD interprets ALL globally
• every visible PDF underlay object may be processed simultaneously
• large page sets can:
  • freeze AutoCAD
  • create geometry overlap
  • generate millions of unnecessary entities
  • corrupt the session

Instead:

• use a crossing window around the active page only
• import pages individually or in small groups

This is significantly safer on production projects.

Step 5 — Configure PDF Import Settings Correctly

Before importing geometry, open:

PDF Import Settings

Recommended settings:

Manager’s Note

Enable:

Remove Underlay After Import

This eliminates the need to manually type:

DETACH

after every conversion cycle.

Step 6 — Optimize PDFIMPORTMODE

The PDFIMPORTMODE variable is a bitcode value, not a simple ON/OFF toggle.

Many users misunderstand this.

Recommended production value:

PDFIMPORTMODE = 51

This commonly enables:

• geometry conversion
• line joining
• linetype inference
• optimized object reconstruction

For BIM environments, standardizing this variable across all workstations prevents inconsistent imports between users.

Step 7 — Repeat the Workflow Efficiently

After importing a page:

• press:

  ENTER

  or:

  SPACEBAR

to repeat the command cycle.

For very large PDFs:

• process 5–10 pages at a time
• save frequently
• run:

  PURGE

  periodically during conversion

Alternative Batch Methods

Method 1 — AutoLISP Automation (Best for CAD Managers)

Full AutoCAD versions support scripted workflows using:

• -PDFIMPORT
• AutoLISP loops
• scripted insertion coordinates

A basic LISP routine can:

• increment page numbers automatically
• insert pages sequentially
• remove underlays after import
• standardize layer placement

This is the preferred workflow for:

• permit archives
• construction submittals
• legacy drawing conversion
• 100+ page consultant packages

AutoCAD LT does not support LISP automation.

Method 2 — Keep PDFs as Underlays Only

If editing is unnecessary:

• do not convert PDFs into geometry

Use:

PDFATTACH

only.

Advantages:

• smaller DWG files
• better performance
• reduced corruption risk
• easier xref management

For BIM coordination workflows, this should be the office standard.

Method 3 — Convert PDF to DWG Externally

Some PDFs are too poorly structured for AutoCAD’s internal importer.

Typical examples:

• scanned drawings
• flattened raster exports
• corrupted consultant PDFs
• mixed vector/raster sheets

In these cases:

• convert externally first
• clean the geometry
• then attach/import into AutoCAD

Common PDF Import Errors

AutoCAD Freezes During PDFIMPORT

Usually caused by:

• dense hatch geometry
• unsupported fonts
• SHX recognition overhead
• massive layer reconstruction

Fixes:

• disable SHX recognition
• reduce imported page count
• split PDFs into smaller batches
• simplify consultant exports

Imported PDF Appears Blank

Cause:

• raster-only PDF
• clipped viewport export
• unsupported transparency effects

Fix:

• test the PDF in Adobe Acrobat
• confirm vector data exists
• re-export from the source CAD platform

Imported Geometry Creates Hundreds of Layers

Cause:

• original PDF contains embedded BIM layer metadata

Common with:

• Revit exports
• Civil 3D sheets
• Navisworks-generated PDFs

Fix:
disable:

Use PDF Layers

or enable:

Use Current Layer

during import.

PDF Imports at the Wrong Scale

Cause:

• incorrect PDF units
• viewport scaling mismatch
• bad plotting calibration

Fix:

• verify original print scale
• confirm insertion units
• test with a known dimension before full conversion

Manager’s Prevention Strategy

1 — Update the Office DWT Template

Create dedicated layers such as:

PDF_IMPORT
PDF_REFERENCE
PDF_UNDERLAY

Apply:

• plotting controls
• transparency
• color standards
• lineweight overrides

This prevents imported geometry from contaminating production layers.

2 — Standardize PDF Export Rules

Require:

• vector PDF exports only
• simplified consultant exports
• consistent page sizes
• controlled layer publishing

Avoid:

• raster plotting
• unnecessary transparency
• embedded image-heavy sheets

3 — Standardize PDFIMPORTMODE Across the Team

Deploy a fixed office value:

PDFIMPORTMODE = 51

This prevents inconsistent imports between users and reduces troubleshooting time.

4 — Disable SHX Reconstruction by Default

Recommended production setting:

PDFSHX = 0

Benefits:

• faster imports
• fewer crashes
• cleaner geometry
• reduced memory usage

Enable SHX recognition only when text reconstruction is absolutely necessary.

5 — Train Teams to Use Underlays First

The correct workflow is:

PDFATTACH → REVIEW → IMPORT ONLY WHAT NEEDS EDITING

Most DWG corruption comes from importing entire consultant sets unnecessarily.

6 — Audit DWG File Size Weekly

Large PDF imports silently inflate projects.

Monitor:

• exploded text
• duplicated geometry
• excessive hatches
• unused layers

Run:

PURGE
OVERKILL
AUDIT

regularly on active projects.

Pro Tip

For unstable consultant PDFs:

Set:

PDFSHX = 0

before importing.

This disables SHX text recognition and prevents AutoCAD from attempting to reconstruct text objects from exploded PDF linework.

On large drawing sets, this can reduce:

• import time
• memory usage
• freezing
• corrupted text entities

Also standardize:

PDFIMPORTMODE = 51

across deployment images for predictable import behavior.

PDFIMPORT vs PDFATTACH — Which Should You Use?

Recommended Screenshot Locations

For a high-authority technical guide, include screenshots for:

1. Attach PDF Underlay dialog
   • multi-page selection area
   • Ctrl/Shift selection
2. PDF Import Settings panel
   • recommended settings enabled
3. Incorrect ALL selection example
   • warning about importing all underlays accidentally
4. Layer explosion example
   • imported BIM layer clutter
5. PDFSHX variable setting
   • command line demonstration

FAQ

Can I import a 50-page PDF into AutoCAD LT automatically?

No.

AutoCAD LT does not support:

• AutoLISP
• scripted batch PDFIMPORT
• automation routines

The fastest supported workflow is:

PDFATTACH

with multi-page underlay placement.

For very large sets:

• split PDFs into smaller groups first.

Why does AutoCAD freeze when importing consultant PDFs?

Usually because:

• SHX recognition is enabled
• the PDF contains dense hatch geometry
• embedded BIM layers are excessive
• too many pages are imported simultaneously

Disable:

PDFSHX

and import smaller page batches.

Why are imported lines spread across dozens of layers?

Because the PDF contains embedded layer metadata from:

• Revit
• Civil 3D
• BIM publishing systems

Disable:

Use PDF Layers

during import if flattened geometry is preferred.

Why do scanned PDFs fail during PDFIMPORT?

Because scanned PDFs contain raster images, not vector geometry.

AutoCAD can only reconstruct:

• vectors
• polylines
• embedded text objects

Raster scans require:

• OCR cleanup
• vectorization software
• manual tracing

Does this workflow work in Civil 3D?

Yes.

Civil 3D uses the same PDF conversion engine as AutoCAD.

However, importing large PDF geometry directly into Civil 3D projects can negatively impact:

• corridor rebuilds
• surface updates
• xref performance
• sheet responsiveness

For production environments:
use underlays whenever possible.