SVG geometry
SVG paths: command endpoints and approximate native geometry
Path data describes geometry; an SVG document can do much more. This inspector deliberately accepts only bounded d data, never arbitrary SVG markup.
Content updated: · Maintainer and corrections
Commands, repetition and arcs
Uppercase commands use absolute coordinates and lowercase commands use coordinates relative to the current point. Repeating parameters can imply another segment; coordinate pairs after the first M imply L. Z closes to the subpath's initial point. Signs, decimals and exponents can separate numbers under SVG grammar.
Arc radii must be nonnegative; large-arc and sweep flags are exactly 0 or 1. The tool rejects malformed syntax rather than asking the browser to display a valid prefix. Up to 100,000 UTF-8 bytes and 2000 segments are accepted, with each numeric parameter and endpoint bounded to absolute 1,000,000. These are editor limits, not the SVG specification's limits.
Endpoints are not a geometry proof
The preview marks the first 200 command endpoints. Curve controls and extrema can lie elsewhere. The native getBBox result describes path fill geometry without stroke; getTotalLength is an approximation in user units and may differ slightly across browsers.
The complete report retains every accepted segment. It is not a stroke-aware collision detector, path optimizer, arbitrary SVG sanitizer or guarantee of mathematically exact arc lengths. Re-test transformed, stroked or animated paths in the receiving document.
Data provenance