History Lesson: What Is a .svg File? Why It Opens in Your Browser

What is a .svg file?

A .svg file is a Scalable Vector Graphics image. Most image formats you know — JPG, PNG, BMP — are raster images: a fixed grid of colored dots (pixels). Enlarge one far enough and the edges turn into stair steps. SVG is a vector format: it stores instructions — move here, draw a curve to there, fill this shape teal — and the software redraws those shapes every time, at whatever size the screen or printer needs. The W3C’s own specification calls SVG “a language for describing two-dimensional vector and mixed vector/raster graphics in XML.”

XML (Extensible Markup Language) is a plain-text format built from tags, much like the HTML of web pages. That means an .svg file is, underneath, text you can open in Notepad: an outer svg tag, then shapes such as path, circle, and rect with their coordinates and colors as attributes. People who search “what is a .svg file” have usually just met one — a logo from a designer, an icon pack, a chart exported from a tool — and found that it does not behave like a photo.

Why does an .svg open in my web browser?

Because on most PCs, the web browser is the program best equipped to draw SVG. Every major browser renders it natively today, so Windows often hands .svg files to Edge, Chrome, or Firefox when you double-click them. Pixel-based tools are built around raster images, and Windows File Explorer has long needed help: Microsoft’s free PowerToys add-ons exist partly to add SVG previews and thumbnails to File Explorer.

Recent Office versions are friendlier. Microsoft says Word, PowerPoint, Excel, and Outlook in Microsoft 365 and in Office 2019, 2021, and 2024 can insert and edit SVG images, and the built-in Icons library in Microsoft 365 apps is made of SVG images. Older Office versions, many websites, and plenty of other programs still expect PNG or JPG.

1998: six proposals for drawing on the web

The early web had pictures, but only as pixels. According to the W3C’s own history page, “The Secret Origin of SVG,” Chris Lilley of the W3C wrote up general requirements for web vector graphics in 1996. By 1998 six competing submissions had arrived. Two came from industry heavyweights: PGML (Precision Graphics Markup Language) from Adobe, IBM, Netscape, and Sun, published as a W3C Note on 10 April 1998, and VML (Vector Markup Language) from Autodesk, Hewlett-Packard, Macromedia, and Microsoft, published on 13 May 1998. The others were Web Schematics, Hyper Graphics Markup Language, WebCGM, and DrawML.

The new SVG Working Group chose not to adopt any of them. Instead it designed a new language “informed by, but not really based on,” the submissions. VML, which began in Microsoft’s Office group and shipped in Internet Explorer, influenced SVG’s compact path syntax: the group found that even after compression, short path codes made files noticeably smaller. PGML, built on the imaging model of Adobe’s PostScript and PDF, most strongly shaped SVG’s coordinate system and transformations and its handling of color.

SVG 1.0, SVG 1.1, and the phones

SVG 1.0 became a W3C Recommendation — the consortium’s word for a finished standard — on 4 September 2001, edited by Jon Ferraiolo of Adobe, with authors from companies as varied as Microsoft, Sun, Netscape, Kodak, Corel, Canon, and Opera. SVG 1.1 followed on 14 January 2003, splitting the language into reusable modules.

The same day, the W3C published Mobile SVG Profiles: SVG Tiny for cellphones and SVG Basic for handheld PDAs, both strict subsets of SVG 1.1. The W3C’s press release noted that the mobile standards group 3GPP was already incorporating Mobile SVG for third-generation phones. A later SVG Tiny 1.2 became a Recommendation on 22 December 2008.

The plugin years: Adobe SVG Viewer and Internet Explorer

A standard needs something to draw it. In the early 2000s the most widely used option was the Adobe SVG Viewer, a free browser plugin; the W3C credits Adobe with producing “a popular SVG viewer” and adding SVG support to products such as Illustrator. Internet Explorer, then the dominant browser, did not draw SVG on its own — Internet Explorer 8 and earlier had no native support — so many people only saw SVG through that plugin.

In December 2005 Adobe completed its acquisition of Macromedia, maker of Flash, the other way to put vector animation on the web. Adobe later discontinued support for the Adobe SVG Viewer on 1 January 2009, saying SVG and its adoption had “matured to the point where it is no longer necessary for Adobe to provide an SVG viewer.” Some in the SVG community linked the decision to Adobe’s new ownership of Flash; Adobe’s notice did not say so.

Browsers were already filling the gap. Opera, Firefox, and WebKit-based Safari and Chrome added native SVG during the 2000s. On 16 March 2010, at its MIX10 conference, Microsoft announced that Internet Explorer 9 would support SVG, and IE9 shipped on 14 March 2011. The W3C’s history page notes the irony: support in Internet Explorer brought SVG “full circle” back to one of its origins, VML.

Inkscape, Illustrator, and the files on your disk

Drawing tools made SVG an everyday export. On 5 November 2003, four developers announced Inkscape, a fork of the Sodipodi drawing program whose stated goal was “a fully SVG-compliant 2D graphics editor”; it uses SVG as its native format. Commercial illustration software such as Adobe Illustrator also saves SVG, and so do many charting, diagram, and design tools.

That is why .svg files pile up on ordinary PCs in 2026: company logos sent by a designer, icon sets downloaded for a website or slide deck, diagrams and charts exported from other tools, and web assets saved from a site. Many are years old — legacy files from finished projects that now need to go into a document, an email, or an upload form that only takes pixels. For the Windows-era vector format that came before, see History Lesson: What Is a .wmf File?.

.svgz: the same drawing, gzip-compressed

Because SVG is text full of repeated tags, it shrinks well under gzip, a widely used lossless compression method (nothing is thrown away). A compressed SVG gets the extension .svgz. The SVG 1.1 specification requires conforming viewers to handle gzip- and deflate-compressed content, and tells web servers to label stored files with “the file extension svgz” as compressed so browsers unpack them correctly.

Outside a browser, .svgz trips up more software than plain .svg: a program that does not unpack it first sees only compressed bytes. The drawing is still there — it just needs a reader that knows to decompress before drawing.

SVG 2: still not finished

For all its ubiquity, SVG’s newest finished standard is still SVG 1.1 Second Edition, a clean-up release published on 16 August 2011. SVG 2 first reached Candidate Recommendation on 15 September 2016. The latest W3C Candidate Recommendation Snapshot of SVG 2 is dated 6 October 2026 and says it can advance to a full Recommendation no earlier than 1 December 2026.

When you need a PNG or JPG instead

Turning an SVG into a normal picture is called rasterizing: software draws the shapes once, at a size you choose, and saves the pixels. Choose a generous size, because once it is pixels it no longer scales cleanly. Pick PNG if the logo or icon needs a transparent background; pick JPG for a flat image on a solid color. Renaming .svg to .png does nothing — the file is still XML text. For more on the target formats, see History Lesson: What Is a .png File?.

Legacy File Converter opens .svg and .svgz files on your own Windows PC and saves them as PNG or JPG images — nothing is uploaded, which matters when the logo belongs to a client. It is not an SVG editor and does not produce vector output; it gives you a picture any app or upload form will take. For neighboring image lessons, see PNG, WMF and EMF, and WebP.