Drop a DXF below to get an instant readiness score, a plain-English list of every problem, and a live before/after preview — all computed right here in your browser. Only the final repaired download costs 1 token.
Analysis, issue list, and preview are 100% free. Nothing about your drawing ever leaves this tab unless you choose to download the repaired file.
Three steps, all in your browser tab. No account, no waiting on a server queue.
Drag a file onto the panel above, or click to browse. It's read locally with the File API — never transmitted.
A 0–100 readiness score plus grouped issue cards explain what's wrong, why it matters, and how each fix works.
Toggle fixes, scrub the before/after slider, and inspect the canvas view. When you're ready, download the repaired DXF for 1 token.
24 checks grouped into blocking problems, quality problems, and informational notes — the same taxonomy CAM software and machine controllers care about.
Every check, the readiness score, the full issue breakdown, and the before/after preview are free forever, with no account required. You only spend a token the moment you click Download repaired DXF.
Most import failures in LightBurn, Fusion 360, and CNC/laser controllers trace back to a small set of geometry problems: splines and arcs left as curves instead of flattened polylines, open contours with a dangling endpoint, duplicate lines drawn twice, or a drawing saved with unitless coordinates. The free checker parses your file's LINE, CIRCLE, ARC, LWPOLYLINE (including bulge arcs), POLYLINE/VERTEX, POINT, SPLINE, ELLIPSE, and INSERT block geometry directly in JavaScript, resolves nested block references with their scale/rotation/mirror transforms, and evaluates the exact same 24-check taxonomy and scoring model used by the DXF Studio repair app — so the score you see here is the same one the paid export is judged against.
Because parsing happens in chunks with a progress callback (and can run inside a Web Worker), even large files in the tens of megabytes stay responsive instead of freezing the tab. Everything above the fold — the drop zone, the readiness score, the grouped issue cards, the canvas viewer with pan/zoom and duplicate/gap highlighting, the layer toggles, and the before/after slider — runs without contacting any server. The single exception is the final “Download repaired DXF” button, which is clearly labeled as the one paid step.
Yes. Uploading is optional and never happens — your file is read and analyzed entirely in your browser. The full readiness score, issue list, plain-English explanations, and the before/after preview are all free with no sign-in. You only spend a token if you choose to download the repaired file.
No. Parsing, checking, and the repair preview all run locally in your browser tab using JavaScript. Nothing is sent anywhere unless you explicitly click Download repaired DXF, at which point only the file and your chosen fix options are sent so the paid export can be generated.
It checks for duplicate and overlapping entities, gaps and open contours, self-intersections, zero-length and zero-area geometry, tiny segments below machine resolution, dense vertex runs, unflattened splines and arcs, non-planar (3D) geometry, unknown or suspicious units, far-from-origin geometry, messy layers, unsupported entity types like text and hatches, and more.
A 0-100 score summarizing how ready your file is to cut or engrave without manual cleanup. Scores of 90 and above are Machine-ready, 60-89 Needs attention, and below 60 Not ready. Each blocking issue costs more points than a quality issue, and each quality issue costs more than an info note.
The check on this page runs entirely inside your browser — your DXF is never uploaded here. Clicking Download repaired DXF opens the DXF Studio app in a new tab on its DXF Doctor tab, where you pick the same file once more and export the repaired copy. That export is the only step that costs a token — 1 token per download.
LINE, CIRCLE, ARC, LWPOLYLINE (including bulge arcs), POLYLINE/VERTEX, POINT, SPLINE, ELLIPSE, and INSERT block references (including nested blocks with scale, rotation, and mirroring) are fully parsed and analyzed. Non-cuttable entities like TEXT, MTEXT, DIMENSION, HATCH, and SOLID are counted and flagged so you know they will be skipped.