How to Convert a CAD PDF to Native Layered DWG
A complete walkthrough of PDF-Plot.com — from uploading your first file to downloading finished native layered DWG deliverables.
Upload your CAD file
Drag and drop your file onto the upload area, or click to browse. PDF-Plot.com accepts three input types, each handled by a different pipeline:
- Vector PDFs — native CAD plots (AutoCAD, Civil 3D, Carlson, or any program) with embedded linework. The geometry is extracted directly — no tracing.
- Text PDFs or deeds — metes-and-bounds prose descriptions. Parsed directly with no image processing.
- Civil 3D interchange ZIPs — packages created inside Civil 3D 2027 by the companion exporter. These carry the source runtime entity inventory, semantic sidecars, generic CAD fallbacks, and every paperspace layout/viewport record. Upload one ZIP by itself.
Scanned or photographed sheets — even saved as PDFs — are flattened raster images with no geometry to extract. PDF-Plot detects and rejects them; re-export the drawing from CAD as a vector PDF instead. A plotted PDF also cannot contain native Civil 3D corridor, surface, alignment, pipe-network, style, or relationship semantics. Use the companion exporter against the source DWG when those details matter.
Open the upload tool →The tier router classifies your file automatically
PDF-Plot.com inspects every uploaded file and routes it to the correct pipeline. The tier badge appears in the results table:
| Badge | File type | Pipeline |
|---|---|---|
| DEED | Text PDF or plain deed description | Regex parser — fastest and most accurate |
| VECTOR | Digital PDF with embedded vector paths | Direct vector extraction — no tracing |
| CIVIL 3D PACKAGE | Versioned ZIP from the Windows companion exporter | Checksum validation, entity reconciliation, layouts, and sidecar reporting |
| NOT VECTOR | Scanned/raster image or flattened PDF | Rejected — PDF-Plot needs native vector geometry |
Review the extracted course table
After processing, the course table lists every extracted bearing and distance. Each entry has a status:
- CLEAN — extracted as-read, no normalization applied.
- REPAIRED — label noise corrected by the bearing repair grammar (e.g.
N8g°29'45"W → N89°29'45"W). Worth a quick visual check. - SKIPPED — token failed a false-positive guard (too many letters, leading digits, known noise word). Not included in the traverse.
If a course you expected to see is missing, check the warnings section. It will identify which label tokens were rejected and why.
Read the closure verdict
The traverse is computed mathematically from the extracted bearings and distances. The closure result tells you whether the boundary closes within survey standards:
| Verdict | Precision | What it means |
|---|---|---|
| PASS | ≥ 1:5,000 | Perimeter ÷ closure error meets survey-grade threshold. Geometry is reliable. |
| REVIEW | < 1:5,000 | Traverse does not close within tolerance. Possible missing course, mislabeled bearing/distance, or open boundary. Check the course table. |
A REVIEW result does not mean the output is wrong — it means the traverse as extracted does not meet the closure threshold. Older deeds written to lower precision standards often produce REVIEW results even when the geometry is correct.
Download your outputs
Vector PDF jobs generate the standard restoration outputs below. Native layered DWG is the CAD deliverable:
- Native layered DWG — AutoCAD-compatible linework restored to the drawing's original layers (e.g.
BOUNDARY,CENTERLINE,EASEMENT,SECTION) recovered from the PDF, each with its original ACI color and linetype — nothing renamed, nothing reassigned. - SVG — proportional vector preview. Open in any browser or Inkscape, or embed in reports.
- JSON manifest — restored layer list with entity counts and verdict; when bearing/distance calls are found on the sheet, it also includes all courses, Cartesian coordinates, closure error, precision ratio, and area (sq ft). Feed into any GIS or database workflow.
The native layered DWG uses a local Cartesian system (survey feet, origin at 0,0). In AutoCAD, run ZOOM → EXTENTS to locate the linework, then move it to your real-world coordinate system using a monument tie point from the source plat. Alternatively, use the Geo-Locate tool to pin your drawing to PLSS section corner coordinates automatically — no CAD editing required.
Civil 3D package jobs instead expose source-preserved.dwg (the native Civil 3D snapshot), generic_fallback.dwg (the portable, lossy Carlson/MicroStation drawing), semantic JSON, source and emitted inventories, layout/viewport JSON, reconciliation JSON, warnings, COGO point CSV, LandXML when available, and a coverage report. The report separates preserved generic CAD from Civil fallback geometry and never presents proxy or unsupported objects as successfully converted.
Automate with the REST API
Every function in the UI is available via the REST API. Use it to process archive batches, integrate with title platforms, or feed results into a GIS database.
| Endpoint | Purpose |
|---|---|
| GET /healthz | Health check |
| POST /api/jobs | Upload files — returns job_id and tier |
| POST /api/jobs/{id}/run | Run pipeline — returns manifest JSON |
| GET /api/jobs/{id}/status | Read processing, complete, or error state |
| GET /api/jobs/{id}/artifact/{name} | Download a manifest-advertised output or sidecar |
# 1. Upload curl -X POST /api/jobs -F "files=@drawing.pdf" # → {"job_id":"abc-123","files":[{"name":"drawing.pdf","tier":"TIER1_VECTOR"}]} # Scanned/raster files are rejected — supply a vector PDF or deed text. # Or upload one companion-exporter package by itself curl -X POST /api/jobs -F "files=@project_c3d_interchange.zip" # → tier: CIVIL3D_PACKAGE # 2. Run curl -X POST /api/jobs/abc-123/run # → {"verdict":"PASS","precision":7842,"closure_ft":0.18,...} # 3. Download a manifest-advertised artifact curl /api/jobs/abc-123/artifact/drawing.dwg -o drawing.dwg
For high-volume processing or custom SLA requirements, contact us for enterprise API access.