SVG Background Remover: Delete a Background Layer, Keep the Paths

Most SVGs that look like they have a white background do have one: a <rect> covering the whole canvas, exported by a design tool and invisible until the file lands on a coloured page. This tool finds that shape, tells you how much of the canvas it covers, and deletes it — or repaints it — without touching a single coordinate of the artwork.

Vector in, vector outTransparent or recolourUndoNo upload

Your SVG

no file yet
Drop an SVG here or click to choose a file.svg up to a few megabytes · nothing is uploaded
Nothing loaded yet.
Drop an SVG above, then remove the background layer on the right.
The download keeps the original viewBox, so the artwork does not move when the background goes.

Background layers

0 found
Load a file and any shape covering at least 90% of the canvas will be listed here.
Action

An SVG background layer is a shape, not a setting: ninety-nine times out of a hundred it is a <rect> whose bounds equal the viewBox and whose fill is white, exported automatically by Figma, Illustrator, Canva or Inkscape. Because it is a real node, the fix is one deletion, and the file that comes out is smaller, transparent and still fully editable.

What counts as a background in this tool

The rule is geometric, not a guess about intent. A node is offered as a background candidate when three things are true: it is a leaf shape (rect, path, circle, ellipse, polygon, polyline, image or use), its bounding box covers at least 90% of the canvas, and it is painted — a shape with fill="none" and no stroke is a layout helper, not a background. Coverage is measured with getBBox() on the parsed file, so a slightly oversized rect (the usual case) still qualifies while a big illustration does not.

What the exporter wroteWhat it looks like in the fileWhat this page does
Artboard fill<rect width="800" height="600" fill="#fff"/> as the first childLists it at 100% coverage, deletes it on Apply
Gradient backdropA rect whose fill is url(#paint0_linear)Same treatment; repainting replaces the gradient with one flat colour
Raster backdrop<image> spanning the canvasListed and deletable; the bitmap goes with it
Bleed or safe-area rectA second rect, identical bounds, sometimes clippedAlso listed, so remove both in one Apply
CSS background on the root<svg style="background:#fff">Not a node — delete the property by hand; the page warns you when it sees one
An SVG logo with a white background rect, the same file after the background layer was deleted shown on a checkerboard, and the same file with the background repainted dark
Left: as exported, a white rect at 100% coverage. Middle: the rect deleted, so the checkerboard shows through. Right: the same rect repainted instead. · swipe to see it all

Delete it, or repaint it

Deleting is the right answer when the SVG will sit on a page whose colour you do not control, when it is destined for a favicon, an icon set or a logo lockup, or when the same file has to work on light and dark. Transparent means the surrounding surface shows through, and that is almost always what you want.

Repainting is the right answer when the file needs to look finished on its own — a social card, a PDF, a slide — and the background is part of the design. It is also the cheapest way to test contrast: paint the background dark, look at the artwork, and decide whether the file needs a light version as well. The byte size barely moves either way, because a fill colour is a few characters; the difference is what the pixels do, not what the file weighs.

Why other fixes do not stick

Three workarounds look like they solve this and do not survive contact with the next tool. A transparent PNG export loses the vector, so the file stops scaling and stops being editable. A CSS background-color on the page only hides the rect — the white shape is still inside the file, waiting to reappear the moment it is opened in an editor or used as a favicon. And a recolour tool will happily change the background's fill to your brand colour, which is a fix only if you wanted a coloured rectangle instead of no rectangle.

Deleting the node is the fix that survives: any consumer of the file — a browser, a laser cutter, a CMS, a build step — sees an SVG with no background because there is no background in it.

When the background is not a rectangle

Rounded cards, die-cut stickers and badge shapes often carry their background as a <path> or a <use> that references a symbol. Both are covered: the check is on the bounding box, not on the tag name, so a squircle that spans the canvas is listed exactly like a rect. What is not covered, and is listed as a warning instead, is a background painted by the root element's style attribute or by a rule inside a <style> block that targets svg or :root. Those are CSS, not nodes, and deleting CSS is a different operation.

If your list is empty, the artwork itself probably has a filled shape running to the edges — a scanned trace, or a logo on a coloured plate. There is nothing to delete in that case: the plate is part of the drawing, and removing it means editing paths, which the SVG Editor is for.

After the background is gone

The file usually gets smaller, so the next stop is SVG Compressor to trim the decimals in the remaining path data, then SVG Validator if the file is going to a cutter or a build pipeline that is strict about ids and references. To use the result as a site icon, Favicon Generator turns it into 16 to 512 px PNGs and a real favicon.svg. If you need a flat bitmap instead — for a marketplace listing that refuses SVG — SVG to PNG exports it with the transparency intact.

Working the other way round, SVG Background Generator does the inverse: it builds waves, blobs or a mesh gradient as a background layer you can put behind the artwork on purpose.

Frequently asked questions

Does removing the background change the artwork?

No. The tool deletes one node — usually a rect that covers the whole canvas — and touches nothing else. Every path, gradient, filter and text element keeps its coordinates, which is the difference between this and a raster background remover: nothing is re-traced, so no edge moves and no colour is quantised.

Why does my SVG have a white background at all?

Because a design tool drew one. Figma, Illustrator and Canva all export the artboard as a filled rect behind the artwork, and some exporters add a second rect for a bleed or a clip path. The shape is invisible while the file sits on a white page and obvious the moment it lands on a coloured card, a dark header or a favicon.

What if the background is a gradient or a photo?

It is still one node. A gradient background is a rect whose fill is url(#someGradient), and an image background is an image element; both cover the canvas and both are listed as candidates. Repainting them replaces the gradient or image with a flat colour, which is usually what you want for a favicon but not for a hero.

Can it remove a background that is not a separate shape?

Not reliably, and you should be suspicious of any tool that claims to. If the background is painted by a parent element's CSS it disappears when the SVG is used on its own; if it is baked into the same path as the artwork there is nothing to delete and you need an editor. The list here shows each candidate's coverage so you can judge whether the match is the real background or part of the drawing.

Is the file uploaded anywhere?

No. The SVG is read with FileReader, parsed with DOMParser and edited in the page. There is no fetch call, no form post and no server that could receive it, which also means the tool keeps working offline once the page has loaded.

Related SVG workflows

More free SVG tools