# Unsupported SVG version specified. This validator only supports SVG 1.1. The recommended way to suppress this warning is to remove the “version” attribute altogether.

> Canonical HTML version: https://rocketvalidator.com/html-validation/unsupported-svg-version-specified-this-validator-only-supports-svg-1-1-the-recommended-way-to-suppress-this-warning-is-to-remove-the-version-attribute-altogether
> Attribution: Rocket Validator (https://rocketvalidator.com)
> License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

This warning appears when an `<svg>` element carries a `version` attribute set to something other than `1.1`, which is the only SVG version the W3C validator checks against. Removing the `version` attribute clears the warning and won't change how browsers draw the graphic.

The `version` attribute was meant to declare which SVG specification the content targets, with values like `"1.0"`, `"1.1"`, or `"2.0"`. The validator can only check inline SVG against SVG 1.1, so when the attribute names a different version it has no ruleset to validate against and falls back to this warning. Browsers ignore the attribute when rendering, so dropping it has no visible effect.

This usually shows up in files exported from drawing tools, which write a `version` attribute by default. The `baseProfile` attribute is obsolete for inline SVG in HTML5 for the same reason, so you can remove it too.

## Invalid example

```html
<svg version="2.0" xmlns="http://www.w3.org/2000/svg" width="100" height="100">
  <rect x="10" y="10" width="80" height="80" fill="teal" />
</svg>
```

## Valid example

```html
<svg xmlns="http://www.w3.org/2000/svg" width="100" height="100">
  <rect x="10" y="10" width="80" height="80" fill="teal" />
</svg>
```

If you have a lot of SVG files to clean up, an optimizer like [SVGO](https://github.com/svg/svgo) can strip the `version` attribute automatically.