Contents
  1. The direct answer
  2. What changes when an element becomes a path
  3. Code patterns for manual conversion
  4. Converting with tools
  5. Why this matters for a favicon specifically
  6. Check what the file actually contains
  7. Rights before modification

Converting an SVG favicon to paths means rewriting its drawing elements, such as rect, circle, ellipse, line, polyline, polygon and text, as path elements whose shape is stored in a d attribute. The rendered result can look the same. The difference is structural: every shape becomes a single, explicit outline that does not depend on shape-specific attributes, installed fonts or stroke settings. This is common practice when preparing a favicon for delivery, because a small icon file is easier to keep consistent when its geometry is fully self-contained.

The direct answer

Every basic SVG shape has an exact path equivalent, so the conversion can be done by hand with a few path commands or automatically with a vector editor or an optimizer. Text and strokes are different cases. Text must be converted to glyph outlines, which needs the actual font. Strokes must be expanded into filled outlines if you want them to behave as solid shapes. Embedded raster images cannot be converted to paths at all. They can only be traced, which produces new, approximate vector artwork.

What changes when an element becomes a path

Original element | Path equivalent | Notes
rect | Move, horizontal and vertical lines, close | Rounded corners (rx, ry) need arc or curve segments
circle / ellipse | Two arc segments, closed | Conversion is exact; some optimizers leave these alone by default
line | Move plus one line segment | Renders only with a stroke; expand the stroke if you need a filled shape
polyline / polygon | Move plus line segments; polygon adds close | Points map directly to coordinates
text | Glyph outlines from the font | Requires the font; the text is no longer editable as text
image (embedded PNG/JPEG) | None | Can only be traced into new, approximate paths

Code patterns for manual conversion

For simple favicon geometry, the conversion follows fixed patterns. In these templates, cx, cy and r are circle values; x, y, w and h are rectangle values. Replace the placeholders with computed numbers, because path data does not accept expressions.

<!-- circle cx cy r  -->
<path d="M (cx-r),cy A r,r 0 1,0 (cx+r),cy A r,r 0 1,0 (cx-r),cy Z"/>

<!-- rect x y w h (square corners) -->
<path d="M x,y H (x+w) V (y+h) H x Z"/>

<!-- polygon points="x1,y1 x2,y2 x3,y3" -->
<path d="M x1,y1 L x2,y2 L x3,y3 Z"/>

<!-- line x1 y1 x2 y2 (stroke still required) -->
<path d="M x1,y1 L x2,y2"/>

Here is a concrete example on a 32-unit canvas. A circle centered at 16,16 with a radius of 12 becomes two arcs, and a rectangle at 8,8 measuring 16 by 16 becomes four straight segments.

<!-- Before -->
<svg viewBox="0 0 32 32">
  <circle cx="16" cy="16" r="12" fill="#1a73e8"/>
  <rect x="8" y="8" width="16" height="16" fill="#ffffff"/>
</svg>

<!-- After -->
<svg viewBox="0 0 32 32">
  <path fill="#1a73e8" d="M4,16 A12,12 0 1,0 28,16 A12,12 0 1,0 4,16 Z"/>
  <path fill="#ffffff" d="M8,8 H24 V24 H8 Z"/>
</svg>

A standalone favicon file also needs the standard SVG namespace declaration on the root svg element. It is omitted above only to keep the snippets short. Shapes that share a fill can be merged into one path by joining their d values. Where shapes overlap, check the fill-rule, because nonzero and evenodd treat overlapping or nested subpaths differently and can open or fill holes unexpectedly.

Converting with tools

  • Inkscape: Path > Object to Path converts shapes and text; Path > Stroke to Path expands strokes into filled outlines.
  • Adobe Illustrator: Type > Create Outlines converts live text; Object > Path > Outline Stroke expands strokes. Basic shapes created in Illustrator are generally exported as paths or shape elements depending on export settings.
  • Figma: Outline stroke expands strokes, and Flatten merges selected layers into a single vector.
  • SVGO: the convertShapeToPath plugin rewrites basic shapes as paths. Circles and ellipses are only converted when its arc conversion option is enabled. Text and strokes are not outlined by this plugin.

Menu names and plugin defaults can change between versions. The evidence supplied for this article did not include version-specific documentation, so confirm the exact command in the version you use.

Why this matters for a favicon specifically

Text is the strongest reason to convert. A text element in an SVG favicon renders with whatever matching font the browser can find. If the brand font is not available, the letterform changes. Outlining the text locks in the intended shapes. Expanding strokes has a similar benefit: it keeps line weights tied to the geometry rather than to stroke attributes, which can behave differently once the icon is scaled down. Paths also keep their fill attributes, so a favicon that switches colors with an internal prefers-color-scheme style rule still works after conversion.

Conversion also has trade-offs. A circle stored as a path no longer has an editable radius. Outlined text cannot be retyped. Any transform attributes may be carried over rather than applied to the coordinates. The usual practice is to keep an editable master file and treat the path-only version as the delivery asset.

Check what the file actually contains

A file ending in .svg is not proof of editable vector paths. Some SVG favicons are wrappers around an embedded PNG or JPEG, stored as an image element with base64 data, and some are exported previews rather than real artwork. Open the markup and look for path and shape elements versus image elements. If the icon is raster underneath, converting to paths means tracing or redrawing it. Traced output is an approximation, not the original artwork.

Rights before modification

Being able to download a favicon or logo does not grant permission to modify it. Converting another organization's mark to paths is a modification of artwork that may be protected by copyright and trademark. Outlining text can also be restricted by the font's license, which may limit embedding or distributing glyph outlines. For your own brand assets, confirm the font license allows outlined use. For anyone else's, get permission from the rights holder.