[3] The early SVG Working Group decided not to develop any of the commercial submissions, but to create a new markup language that was informed by but not really based on any of them.
Early adoption was limited due to lack of support in older versions of Internet Explorer.
Native browser support offers various advantages, such as not requiring plugins, allowing SVG to be mixed with other content, and improving rendering and scripting reliability.
[22] SVG supports interactivity, animation, and rich graphical capabilities, making it suitable for both web and print applications.
SVG images can be compressed with the gzip algorithm, resulting in SVGZ files that are typically 20–50% smaller than the original.
The feature set includes nested transformations, clipping paths, alpha masks, filter effects and template objects.
SVG has the information needed to place each glyph and image in a chosen location on a printed page.
In particular, SVG Tiny was defined for highly restricted mobile devices such as cellphones; it does not support styling or scripting.
In 2003, the 3GPP, an international telecommunications standards group, adopted SVG Tiny as the mandatory vector graphics media format for next-generation phones.
SVG images, being XML, contain many repeated fragments of text, so they are well suited for lossless data compression algorithms.
This code will produce the colored shapes shown in the image, excluding the grid and labels: The use of SVG on the web was limited by the lack of support in older versions of Internet Explorer (IE).
Some earlier versions of Firefox (e.g. versions between 1.5 and 3.6[54]), as well as a few other, now outdated, web browsers capable of displaying SVG graphics, needed them embedded in