Skip to main content
Vecaria

DXF Pocketing G-code

Local

Generate pocketing G-code from closed DXF contours — contour-parallel clearing, stepover, multi-depth passes, tool-radius compensation. No upload. Pro feature.

Tool
Feeds & spindle
Depth
Output

Circles are approximated as 64-segment polylines (no true arc interpolation); wall contours follow the approximated polylines.

What is it? CAM Pocket generates 2.5D pocketing G-code from closed DXF contours: contour-parallel clearing with a selected stepover, multi-depth passes and tool-radius compensation.

TL;DR: Generate contour-parallel pocketing G-code from closed DXF contours — set stepover, depth and feed, preview the passes, then download pocket.gcode. No upload, computed in your browser.

How to use

  1. Paste ASCII DXF text with closed contours (circles/polylines).
  2. Set tool diameter, stepover, depth and feed.
  3. Click Run, then copy or download pocket.gcode.

FAQ

What clearing strategy is used?

Contour-parallel (offset) clearing with the stepover you choose.

Is it local?

Yes, the toolpath is computed locally.

Is it free?

No — CAM Pocket is a Pro feature; on the Free plan this page shows an upgrade prompt.

How is this different from the DXF to G-code tool?

That tool traces the outline in a single pass for laser cutters and engravers. CAM Pocket clears the material inside a closed contour with offset passes at a stepover you choose, in multiple depth cuts — the 2.5D pocketing strategy used on a milling machine or router.

Is clearing contour-parallel or zigzag?

Contour-parallel (offset) only: the first ring finishes the wall, then each ring steps inward by your stepover up to 100% of tool diameter. Zigzag or line-based clearing is not available.

What shapes can I pocket?

Any closed contour the DXF whitelist accepts — circles (sampled to 64 segments, not arc interpolation) and closed polylines, including irregular shapes. Each closed contour is cleared independently; islands and rest material are not detected.

Does it add lead-in, lead-out or ramp entry?

No — the tool plunges straight down at the contour start. Set plunge and feed rates accordingly, add tabs if the part must stay connected, and dry-run above the material before cutting.

Which controllers are supported?

Output is generic G-code (G21 mm, G90 absolute) with no controller-specific post-processor. GRBL, Mach3 and Fanuc users typically run it after a dry check; we do not generate controller-specific dialects.

Examples

  • Paste DXF with circles/closed polylines → set tool diameter and stepover → download the pocket G-code

Supported formats

DXFG-code

Limitations

  • 2.5D pocketing only; no 3D surfacing.
  • Closed contours are cleared one by one — no island/rest-material awareness.
  • Contours must be closed for correct results.
  • No lead-in/lead-out moves — the tool plunges straight down at the contour start; angled or arc lead-in is not implemented.
  • Entity types outside the toolpath whitelist (e.g. SPLINE/INSERT/HATCH) produce no toolpath — the result panel reports per-type counts.
  • Processed locally in your browser — nothing is uploaded.

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.