Vector graphics are very useful in many circumstances — they have small file sizes and are highly scalable, so they don't pixelate when zoomed in or blown up to a large size. In this article we'll show you how to include one in your webpage.
|Prerequisites:||You should know the basics of HTML and how to insert an image into your document.|
|Objective:||Learn how to embed an SVG (vector) image into a webpage.|
Note: This article doesn't intend to teach you SVG; just what it is, and how to add it to web pages.
On the web, you'll work with two types of images — raster images, and vector images:
- Raster images are defined using a grid of pixels — a raster image file contains information showing exactly where each pixel is to be placed, and exactly what color it should be. Popular web raster formats include Bitmap (
.bmp), PNG (
.png), JPEG (
.jpg), and GIF (
- Vector images are defined using algorithms — a vector image file contains shape and path definitions that the computer can use to work out what the image should look like when rendered on the screen. The SVG format allows us to create powerful vector graphics for use on the Web.
To give you an idea of the difference between the two, let's look at an example. You can find this example live on our Github repo as vector-versus-raster.html — it shows two seemingly identical images side by side, of a red star with a black drop shadow. The difference is that the left one is a PNG, and the right one is an SVG image.
The difference becomes apparent when you zoom in the page — the PNG image becomes pixelated as you zoom in because it contains information on where each pixel should be (and what color). When it is zoomed, each pixel is increased in size to fill multiple pixels on screen, so the image starts to look blocky. The vector image however continues to look nice and crisp, because no matter what size it is, the algorithms are used to work out the shapes in the image, with the values being scaled as it gets bigger.
Note: The images above are actually all PNGs — with the left-hand star in each case representing a raster image, and the right-hand star representing a vector image. Again, go to the vector-versus-raster.html demo for a real example!
Moreover, vector image files are much lighter than their raster equivalents, because they only need to hold a handful of algorithms, rather than information on every pixel in the image individually.
SVG is an XML-based language for describing vector images. It's basically markup, like HTML, except that you've got many different elements for defining the shapes you want to appear in your image, and the effects you want to apply to those shapes. SVG is for marking up graphics, not content. At the simplest end of the spectrum, you've got elements for creating simple shapes, like
<rect>. More advanced SVG features include
<feColorMatrix> (transform colors using a transformation matrix,)
<animate> (animate parts of your vector graphic,) and
<mask> (apply a mask over the top of your image.)
As a simple example, the following code creates a circle and a rectangle:
<svg version="1.1" baseProfile="full" width="300" height="200" xmlns="http://www.w3.org/2000/svg"> <rect width="100%" height="100%" fill="black" /> <circle cx="150" cy="100" r="90" fill="blue" /> </svg>
This creates the following output:
From the example above, you may get the impression that SVG is easy to handcode. Yes, you can handcode simple SVG in a text editor, but for a complex image this quickly starts to get very difficult. For creating SVG images, most people use a vector graphics editor like Inkscape or Illustrator. These packages allow you to create a variety of illustrations using various graphics tools, and create approximations of photos (for example Inkscape's Trace Bitmap feature.)
SVG has some additional advantages besides those described so far:
- Text in vector images remains accessible (which also benefits your SEO).
So why would anyone want to use raster graphics over SVG? Well, SVG does have some disadvantages:
- SVG can get complicated very quickly, meaning that file sizes can grow; complex SVGs can also take significant processing time in the browser.
- SVG can be harder to create than raster images, depending on what kind of image you are trying to create.
- SVG is not supported in older browsers, so may not be suitable if you need to support older versions of Internet Explorer with your web site (SVG started being supported as of IE9.)
Raster graphics are arguably better for complex precision images such as photos, for the reasons described above.
Note: In Inkscape, save your files as Plain SVG to save space. Also, please refer to this article describing how to prepare SVGs for the Web.
In this section we'll go through the different ways in which you can add SVG vector graphics to your web pages.
To embed an SVG via an
<img> element, you just need to reference it in the src attribute as you'd expect. You will need a
height or a
width attribute (or both if your SVG has no inherent aspect ratio). If you have not already done so, please read Images in HTML.
<img src="equilateral.svg" alt="triangle with all three sides equal" height="87" width="100" />
- Quick, familiar image syntax with built-in text equivalent available in the
- You can make the image into a hyperlink easily by nesting the
- The SVG file can be cached by the browser, resulting in faster loading times for any page that uses the image loaded in the future.
- If you want to control the SVG content with CSS, you must include inline CSS styles in your SVG code. (External stylesheets invoked from the SVG file take no effect.)
- You cannot restyle the image with CSS pseudoclasses (like
For browsers that don't support SVG (IE 8 and below, Android 2.3 and below), you could reference a PNG or JPG from your
src attribute and use a
srcset attribute (which only recent browsers recognize) to reference the SVG. This being the case, only supporting browsers will load the SVG — older browsers will load the PNG instead:
<img src="equilateral.png" alt="triangle with equal sides" srcset="equilateral.svg">
You can also use SVGs as CSS background images, as shown below. In the below code, older browsers will stick with the PNG that they understand, while newer browsers will load the SVG:
background: url("fallback.png") no-repeat center; background-image: url("image.svg"); background-size: contain;
If your SVGs aren't showing up at all, it might be because your server isn't set up properly. If that's the problem, this article will point you in the right direction.
You can also open up the SVG file in a text editor, copy the SVG code, and paste it into your HTML document — this is sometimes called putting your SVG inline, or inlining SVG. Make sure your SVG code snippet begins and ends with the
<svg></svg> tags (don't include anything outside those.) Here's a very simple example of what you might paste into your document:
<svg width="300" height="200"> <rect width="100%" height="100%" fill="green" /> </svg>
- Putting your SVG inline saves an HTTP request, and therefore can reduce a bit your loading time.
- You can assign
ids to SVG elements and style them with CSS, either within the SVG or wherever you put the CSS style rules for your HTML document. In fact, you can use any SVG presentation attribute as a CSS property.
- Inlining SVG is the only approach that lets you use CSS interactions (like
:focus) and CSS animations on your SVG image (even in your regular stylesheet.)
- You can make SVG markup into a hyperlink by wrapping it in an
- This method is only suitable if you're using the SVG in only one place. Duplication makes for resource-intensive maintenance.
- Extra SVG code increases the size of your HTML file.
- The browser cannot cache inline SVG as it would cache regular image assets, so pages that include the image will not load faster after the first page containing the image is loaded.
- You may include fallback in a
<foreignObject>element, but browsers that support SVG still download any fallback images. You need to weigh whether the extra overhead is really worthwhile, just to support obsolescent browsers.
You can open SVG images in your browser just like webpages. So embedding an SVG document with an
<iframe> is done just like we studied in From <object> to <iframe> — other embedding technologies.
Here's a quick review:
<iframe src="triangle.svg" width="500" height="500" sandbox> <img src="triangle.png" alt="Triangle with three unequal sides" /> </iframe>
This is definitely not the best method to choose:
iframes do have a fallback mechanism, as you can see, but browsers only display the fallback if they lack support for
In this active learning section we'd like you to have a go at playing with some SVG for fun. In the Input section below you'll see that we've already provided you with some samples to get you started. You can also go to the SVG Element Reference, find out more details about other toys you can use in SVG, and try those out too. This section is all about practising your research skills, and having some fun.
If you get stuck and can't get your code working, you can always reset it using the Reset button.
This article has provided you with a quick tour of what vector graphics and SVG are, why they are useful to know about, and how to include SVG inside your webpages. It was never intended to be a full guide to learning SVG, just a pointer so you know what SVG is if you meet it in your travels around the Web. So don't worry if you don't feel like you are an SVG expert yet. We've included some links below that might help you if you wish to go and find out more about how it works.
In the last article of this module we will explore responsive images in detail, looking at the tools HTML has to allow you to make your images work better across different devices.
- SVG tutorial on MDN
- Quick tips for responsive SVGs
- Sara Soueidan's tutorial on responsive SVG images
- Accessibility benefits of SVG
- How to scale SVGs (it's not as simple as raster graphics!)