Convert DXF drawings to SVG, PDF or PNG locally - for the web, print and preview. No upload.
Running locally on your device ...
Running locally on your device ...
0%
Your files never left your device
Continue with this file
No re-upload neededThese tools accept .SVG - your file is handed over directly.
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
DXF (Drawing Exchange Format) is AutoCAD's text-based interchange format: almost every CAD, CAM and laser-cutting program can read and write it without needing the origin program's own native drawing file. Viewing a DXF drawing in a browser, embedding it in a web page (SVG), printing it (PDF) or using it as a thumbnail (PNG) normally needs a CAD program. This tool reads the drawing directly in the browser and renders it into one of the three formats.
Supported are LINE, LWPOLYLINE/POLYLINE (including curved bulge segments), CIRCLE, ARC, ELLIPSE, POINT, TEXT, MTEXT (plain text, formatting codes stripped), INSERT block references (including nested blocks and column/row arrays), SPLINE (evaluated as a real rational NURBS curve, not just a polyline through the raw control points) and solid-fill HATCH. DIMENSION and pattern hatching (e.g. ANSI31) - the most elaborate and least common element types in real drawings - are deliberately not rendered, nor is any other unrecognised element type.
If a drawing contains such unsupported elements, everything the tool CAN read is still rendered - nothing is silently omitted: a second, small text file then lists exactly which element types and how many were skipped. Everything runs entirely locally in the browser; your possibly confidential engineering drawing never leaves your device.
| Input formats | DXF |
|---|---|
| Auto-conversion | PNG, JPG, WebP, SVG |
| Output formats | SVG, PDF, PNG |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Renders LINE/LWPOLYLINE/POLYLINE (incl. bulge arcs)/CIRCLE/ARC/ELLIPSE/POINT/TEXT/MTEXT (plain text)/INSERT (incl. nested blocks and column/row arrays)/SPLINE (as a real rational NURBS curve, evaluated via the De Boor algorithm)/solid-fill HATCH. Pattern hatching (e.g. ANSI31), DIMENSION and any other unrecognised element type are not rendered - skipped elements are honestly listed in an additional notice file, never silently dropped. A drawing consisting ENTIRELY of unsupported elements is rejected with a clear error instead of producing an empty file.
LINE, LWPOLYLINE/POLYLINE (with bulge arcs), CIRCLE, ARC, ELLIPSE, POINT, TEXT, MTEXT, INSERT block references, SPLINE (a real NURBS curve) and solid-fill HATCH. DIMENSION and pattern hatching are not included.
They are skipped, but not hidden: an additional text file lists exactly which element types and how many were not rendered. A solid-fill HATCH, by contrast, is rendered normally.
Yes, the drawing coordinates are carried over 1:1 - no unit is assumed or converted.
Yes, in the SVG and PDF export - they are drawn as real arc paths, not broken into straight segments.
No, the conversion happens entirely locally in the browser; your drawing never leaves your device.
SVG to DXF · DXF to GeoJSON · SVG to PNG · PNG to SVG · STL to OBJ · TopoJSON to GeoJSON