How to Fix a Corrupted SVG File

The short answer

Most broken SVG files can be fixed because SVG (Scalable Vector Graphics) is plain text. It is an XML document that describes shapes, paths, colors and text with markup, not pixels. When a logo SVG will not open or renders wrongly, the cause is usually one of a few problems: malformed XML, a missing namespace declaration, a broken or missing viewBox, references to gradients, masks, fonts or images that no longer resolve, or a file that is not really SVG despite its extension. Work on a copy. Open it in a text editor and use an XML validator or a web browser to find where parsing fails. Correct that spot, then confirm the result in more than one renderer. If you still have the original design file, re-exporting from it is often faster and more reliable than repairing the damaged export.

An SVG fixer, whether an online tool, an editor command or an optimizer, can only automate these same checks. It cannot recover geometry that was never saved. If the file is truncated and the source artwork is gone, the missing parts must be redrawn.

Terms used in this guide

• XML: the strict markup syntax SVG is written in. A single unclosed tag or stray character can stop the whole file from rendering.
• Namespace (xmlns): the attribute on the root svg element that tells software the markup is SVG. Without it, some programs show raw text or nothing at all.
• viewBox: four numbers (min-x, min-y, width, height) that define the coordinate area of the artwork. If they are wrong, the logo can appear cropped, tiny, off-canvas or invisible.
• defs and IDs: reusable definitions such as gradients, clip paths, masks and symbols, each referenced by an id. Broken references make fills disappear or turn black.
• Outlined text: lettering converted into vector paths, so it no longer depends on a font being installed.
• SVGZ: a gzip-compressed SVG. It looks like binary data if opened as text.

Step 1: Protect the original and confirm what the file actually is

Duplicate the file before you change anything. Then confirm the file type, because a .svg extension does not prove the file contains vector data. It might be a renamed PNG or JPEG, a compressed SVGZ, an empty zero-byte file left by a failed download, or an SVG that only wraps an embedded raster image. On macOS or Linux, you can check the type and the first bytes from a terminal:

file logo.svg
head -c 300 logo.svg

A healthy SVG begins with readable text, usually an optional XML declaration followed by an svg element. Garbled binary output suggests compression or a different format. If it is gzip-compressed, decompress it to plain SVG:

gunzip -c logo.svgz > logo.svg

Step 2: Find the exact parse error

Open the file directly in a web browser. Browsers report XML errors with a line and column number, which points you to the damage. A command-line validator such as xmllint, where installed, does the same without rendering anything:

xmllint --noout logo.svg

No output means the XML is well formed. Any problems that remain are in the SVG content itself, such as the viewBox, references or styles, rather than in the syntax.

Step 3: Repair the markup

Symptom | Likely cause | Fix

Error about an unexpected end of file | File truncated during save, export or transfer | Re-export from source, or close open tags by hand if only the ending is missing; lost paths cannot be recovered

Error naming an entity or an ampersand | Unescaped & or < in text, metadata or a font name | Replace & with & and < with < inside text and attribute values

Mismatched or unclosed tag | Manual edit or faulty export | Close or remove the element at the reported line

File shows as text or a blank page | Missing xmlns on the svg element | Add xmlns="http://www.w3.org/2000/svg" to the root element

Content before the root element | Stray characters, a byte order mark or a duplicated XML declaration | Delete everything before the XML declaration or the svg tag

Garbled characters | Encoding mismatch | Save as UTF-8 and make sure the XML declaration, if present, says UTF-8

Once repaired, a minimal root element for a logo should look structurally like this, with your own coordinates in place of the placeholder values:

<?xml version="1.0" encoding="UTF-8"?>
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 WIDTH HEIGHT">
  <!-- logo paths here -->
</svg>

If the file uses xlink:href attributes, the root element also needs the declaration xmlns:xlink="http://www.w3.org/1999/xlink". Without it, older references fail to parse.

Step 4: Fix rendering problems in well-formed files

• Cropped, invisible or wrongly sized logo: check that the viewBox exists, contains four numbers and actually covers the artwork's coordinates. Fixed width and height values that conflict with the viewBox can also distort scaling.
• Missing or black fills: search for every url(#...) and href="#..." reference and confirm that a matching id exists in defs. Copy-pasting between files often breaks these links or creates duplicate IDs.
• Wrong or substituted lettering: live text depends on installed fonts. For logo delivery, convert the text to outlines in the source file and re-export.
• Missing photos or textures: linked images point to paths on the original computer. Embed them, or better, confirm whether a raster element belongs in a vector logo at all.
• Styles that disappear in some programs: CSS in a style block or class-based styling is not supported equally everywhere. Many vector editors can export styles as presentation attributes, which are read more consistently.

Step 5: Let a vector editor rebuild the file, then clean it carefully

After the XML parses, opening the file in a vector editor such as Inkscape, Adobe Illustrator or Affinity Designer and saving a fresh copy often rewrites inconsistent markup into a clean structure. Where the option exists, choose plain or standard SVG rather than an editor-specific format. Editor-specific formats carry extra metadata that other software may ignore or mishandle.

Optimizers such as SVGO can shrink and tidy files, but aggressive settings can remove the viewBox, merge paths, round coordinates or strip IDs that other elements rely on. Treat optimization as a separate step and verify again afterward. Be cautious with online SVG fixers for unreleased or client logos. Uploading the file sends the artwork to a third party, so check the service's handling terms first.

Step 6: Verify the repaired logo before delivery

• Validate again: the file should pass an XML check without errors.
• Render in at least two different browsers and one vector editor, and compare the results with an approved reference of the logo.
• Inspect it in outline or wireframe view to confirm the artwork is made of paths, not an embedded bitmap.
• Zoom far in: edges should stay sharp, and curves should show no stray points, gaps or overlapping duplicates.
• Check colors against the brand specification, since repairs and re-exports can shift color values or drop gradients.
• Confirm that text is outlined and that no external files are referenced.
• Test it at the smallest and largest sizes it will be used, including on both light and dark backgrounds if the logo has variants.

When repair is not the right decision

Repair what can be verified, and rebuild what cannot. If large parts of the geometry are missing, or the SVG turns out to wrap only a low-resolution bitmap, patching the markup will not produce production-ready artwork. Get the original source file from the designer or brand owner, or redraw the logo as clean vector paths. A successful repair also says nothing about usage rights. Fixing a file does not grant permission to reuse a logo you do not own or have not licensed.

Gaps in this guide

No verified evidence was available about specific SVG repair tools, their accuracy or their pricing, so none are rated or recommended here. The tools named above are general examples, and their exact menus and export options vary by version. Check the current documentation for the software you use.