GeoJSON to DXF Converter
LocalConvert GeoJSON to DXF for CAD or laser cutting. Points, lines and polygons become polylines, layers map from properties. Free, no sign-up, nothing uploaded.
Sample data loaded — click "Convert to DXF" to try it.
Unit declares what your coordinate values already are (written to the DXF $INSUNITS header); values are never rescaled. Keep Unitless for WGS84 lon/lat — degrees are not a physical length (converting needs reprojection; use GeoJSON Reproject first). Y is written as-is: latitude is north-positive, so north stays up (no mirroring). "Y flip" is only for Y-down source data such as pixel coordinates.
What is it? GeoJSON to DXF converts GeoJSON points, lines and polygons to DXF for CAD and laser cutting.
TL;DR: GeoJSON to DXF converts points, lines, polygons and their Multi variants into DXF polylines and points for CAD or laser cutting — layers come from properties.layer (falling back to properties.name, then layer 0). Paste or drop a GeoJSON file, convert, check the on-page line preview, then download the .dxf. Free with no sign-in; everything runs locally in your browser and nothing is uploaded.
How to use
- Paste your GeoJSON text in the input area (a sample is prefilled), or click "or load a file" to pick/drop a .geojson/.json file.
- Click "Convert to DXF" (or press Ctrl/Cmd+Enter) — the result area shows the converted/skipped counts.
- Inspect the on-page line preview of the generated DXF (same parser as DXF → SVG), then copy the DXF text or download it as a .dxf file.
FAQ
Which geometries are supported?
Point, LineString, Polygon and their Multi variants.
How do DXF layers map from GeoJSON?
Layers come from GeoJSON properties.layer (falling back to properties.name, then layer 0); Y is written as-is (latitude north-positive, so north stays up) and the unit declaration defaults to Unitless ($INSUNITS=0) — see limitations.
Is it local?
Yes.
What units are the DXF coordinates in?
The unit declaration defaults to Unitless ($INSUNITS=0) and coordinates are written exactly as in your GeoJSON — values are never rescaled. If your data is WGS84 longitude/latitude, the numbers stay in degrees; declare mm or m only when your values already are in those units. For projected units, reproject the GeoJSON first (see the GeoJSON Reproject tool).
Will the DXF open in AutoCAD or my laser-cutting software?
The output is ASCII DXF: lines and polygons become LWPOLYLINE entities, points become POINT entities — AutoCAD, QCAD, ZWCAD and common laser-cutting software open it directly. The on-page preview is a line rendering for a quick geometry check; open the .dxf in CAD or laser software for full fidelity.
How big can my file be?
Nothing is uploaded, so there is no upload cap — the real bound is your device's memory. Parsing and conversion run in the browser, and the result area reports how many features were converted and how many were skipped.
Examples
- Input: a GeoJSON Feature whose geometry is a LineString (pasted text)
- Output: an LWPOLYLINE on layer "roads" (DXF text you can copy or download as .dxf)
Supported formats
Limitations
- Point/LineString/Polygon and Multi variants are supported.
- The on-page preview is a line rendering of the generated DXF (geometry check), not a CAD workspace — open the .dxf in CAD/laser software for full fidelity.
- Geometry only: attribute tables are not written (properties.layer becomes the DXF layer name).
- Y is written as-is: latitude is north-positive so north stays up (no mirroring; the "Y flip" option is only for Y-down source data such as pixel coordinates). The unit declaration defaults to Unitless ($INSUNITS=0) — declare mm/m only when your values already are; values are never rescaled. Z elevations are dropped.
- No reprojection.
Privacy
Privacy first: this tool runs entirely in your browser — your input and files never leave your device, and everything is cleared when you close the page.
Related tools
Standards & comparison
| Dimension | Vecaria (this tool) | Online converters (cloud) | Desktop professional CAD |
|---|---|---|---|
| Privacy | Runs locally in your browser; the file is not uploaded | You upload the file to a third-party server | Runs locally |
| Wait | No queue — as fast as your own device | Upload plus cloud queue | Local application startup |
| Standards support | GeoJSON (RFC 7946) · DXF (AutoCAD ASCII) | Varies by service, often older subsets | Full vendor protocol sets |
| Install footprint | 0 MB — runs in the browser | 0 MB | Several GB of storage |