Vecline

Useful for

Use cases llm-inferred

Vectorise flat logos, diagrams and schematic graphics to SVG for editable report figures · Export site-plan or schematic graphics to DXF at real physical size for CAD import · Render client PDF or Office reports to raster or SVG for figure reuse and review · Convert legacy raster figures (TIFF, BMP, TGA) to PNG or WebP for submissions

Audience llm-inferred

GIS analysts · BIM and civils engineers (DXF/EPS output) · drainage and environmental report authors · developers building MCP agent tooling

Limitations

Constraints llm-inferred

Photographs and complex art are traced approximately, not exactly; accuracy is measured per conversion, not guaranteed · Default sub-pixel tracing costs about 2.35x the gzipped bytes; --no-subpixel reverts this · Pixel-mode on a photo yields very large output (about 1.99 MB, 42,933 shapes, for the docs' example) · An embedded JPEG round-trips byte-for-byte but does not render bit-identically · HEIC, JPEG XL, JPEG 2000, PSD and camera RAW are not built in; PDF is listed as not built in yet PDF rendering is supported, so this needs clarification · Not the fastest: imagetracerjs was quicker on every fixture measured · Reading image files, SVG rendering and the lossless guarantee need native codecs (sharp/resvg); vecline/core has no file I/O or SVG rendering · ICO entries holding PNG payloads need a PNG codec when native packages are omitted · Entry metadata lists VECLINE_TOKEN API key auth, which DOCS do not mention; unverified · DOCS say 'Ten raster formats' while entry metadata says 11 raster formats (the table lists 10 raster formats plus SVG) · No georeferencing, CRS or geodata handling is described in DOCS

Example tool calls docs-verified

{
  "tool": "lossless",
  "arguments": {}
}

{
  "tool": "pixel",
  "arguments": {}
}

{
  "tool": "trace",
  "arguments": {}
}