File Formats: Choosing SVG, PNG, JPG, and WebP for a Design System
Learn which image file types a design system should use, when to pick each one, and how to export them so developers get the same clean files.
In short
A design system picks image file types such as SVG, PNG, JPG and WebP by content, and exports them so developers get the same clean files.
12 min readFree
What You Will Learn
A design system is a shared set of parts and rules that a whole product team uses. Part of that shared set is the file type each picture uses. A picture or graphic that a product needs, such as an icon, a logo, or a photo, is called an asset. This lesson explains the common file formats, when each one is the right choice, and how to export assets so developers receive the same clean files every time.
By the end, you should be able to pick a format for an asset, explain why you picked it, and describe the export set a team should hand over.
Key words
- Asset
- Any picture or graphic a product uses, such as an icon, a logo, or a product photo.
- File format
- The type of file a picture is saved as, such as SVG or PNG. It decides how the picture is stored and what it can do.
- Vector
- A picture built from shapes that are described by numbers, so it can grow or shrink without losing sharpness.
- Raster
- A picture built from a grid of tiny colored squares called pixels.
- Transparency
- Parts of a picture that are see-through, so the background shows through them.
- Lossless and lossy
- Lossless saving keeps every detail. Lossy saving throws away some detail to make the file smaller.
- Fallback
- A backup file that is used when a browser or tool cannot show the first choice.
- Export
- Saving a design from the design editor as a separate file.
- Handoff
- The moment a designer passes finished files and notes to the developers who build the product.
- Scale variant
- The same asset saved at more than one size, such as 1x (standard), 2x (double), and 3x (triple).
Should You Choose Vector or Raster First?
Almost every format decision starts with one question. Is the asset a drawing made of clean shapes, or is it a picture made of many small colored dots? The answer splits the formats into two families.
Vector (SVG)
SVG stands for Scalable Vector Graphics. It describes shapes with coordinates, not pixels. Because of that, it can be shown at any size and stay sharp, and it can also keep a transparent background. Use it for icons, logos, and simple illustrations.
Raster (PNG, JPG, WebP, AVIF)
A raster file stores a fixed grid of pixels. It looks right at the size it was made, and it can look soft when it is stretched. Raster files suit photos and complex images, where the detail is too rich to draw with simple shapes.
Tip
Before you pick a format, ask yourself whether the asset would still look clean if it were ten times bigger. If yes, it is probably a vector. If no, it is probably a raster.
How Do You Match the Format to the Content?
Once you know the family, pick the exact format by looking at what is inside the picture. Each format has strengths that suit a certain kind of content. The list below is a simple starting point for a design system's standard set.
SVG for icons, logos, and simple illustrations
Use SVG when the asset is made of shapes and lines. Figma's help center says SVG suits logos, icons, and illustrations that will appear in responsive designs. Because the file is small and stays sharp, it is the usual choice for icons across a product.
PNG for transparency and sharp screenshots
PNG is a lossless raster format that supports transparency. It keeps text readable, which makes it a good match for screenshots, charts, and graphics that mix pictures with text. Its files are usually bigger than JPG files.
JPG for photos with no transparency
JPG is a lossy format. It makes photos small, which helps pages load faster. It does not support transparency, so any see-through area is flattened into a solid color, often white. Heavy compression can also blur small text, so keep JPG away from text-heavy images.
WebP and AVIF are newer formats. They aim to give smaller files than JPG and PNG while keeping good quality. They are not always the best first choice, because older browsers and some tools may not open them.
Tip
Pick the format by the content, not by habit. A photo, a logo, and a settings screenshot should almost never use the same format.
The next two sub-topics show how the raster formats are used in practice, and what to do when a team wants to use the modern ones.
PNG and JPG in Practice
Choose PNG when a picture needs a see-through background, such as a logo that sits on a colored banner. Choose PNG when the image has small text, since lossy formats can smear letters. A screen capture of a settings page with small labels is a good example.
Choose JPG when the picture is a photo and needs no transparency. A product photo on a plain white background is a good example. The team saves some quality for a much smaller file, and most people cannot see the difference at normal size. If a photo must be placed over a colored background, do not export it as JPG, because the background would be filled with a solid color.
WebP and AVIF as Modern Options
WebP can be lossy or lossless, and it supports transparency. One comparison notes that lossless WebP often beats PNG on file size. Another says that WebP is the common choice for modern websites. Still, lossy WebP can blur thin colored text, so a lossless setting is safer for screenshots.
AVIF is a newer format that can make even smaller photo files. Some legacy browsers have gaps in AVIF support. That is why many teams use AVIF or WebP as the first choice and keep a JPG as the fallback. A fallback means the backup file that loads when the first choice cannot be shown.
Tip
When you use WebP or AVIF, always name the backup format in the handoff notes. Developers should never have to guess which file to use if the modern format is not supported.
What Are the Export and Handoff Conventions?
A design system should not leave export choices to each designer. A team agrees on a standard set of formats, sizes, names, and settings, and writes them down. The steps below show a simple version of that agreement.
- 1
Agree on the standard set
List the formats the team will deliver for each asset type. For example, icons as SVG, logos as SVG plus PNG, and photos as WebP with a JPG fallback.
- 2
Choose the scale variants
For raster assets, decide which sizes to export, usually 1x, 2x, and 3x. Vector assets usually need only one file.
- 3
Set the export settings once
In the design editor, add the export rows to the asset itself. Figma lets you click the plus button more than once, so one click can save several rows at the same time.
- 4
Name every file the same way
Use one pattern for all files. A scale can be added with a suffix such as @2x.
- 5
Optimize and organize
Compress PNG and JPG files before delivery to keep them small. Store them in folders by format and by density, so developers can find the right file fast.
- 6
Write the handoff note
Record which formats exist, where each file lives, when to use each one, and why each format was chosen. Developers then know what to build with.
Two sub-topics go deeper into scale variants and into naming and optimization. Naming rules are covered in their own lesson, so here we only show how names support the handoff.
What Are the Scale Variants 1x, 2x, and 3x?
A scale variant is the same raster asset saved at a larger size. Think of 1x as the standard size and 2x as double. Phones and laptops with high-density screens pack more pixels into the same space, so a 1x image can look soft on them. Figma's guides suggest 2x for most screen use and 3x for images people might zoom into.
Here is a simple example. A 24 by 24 pixel icon is exported at 24 by 24 pixels for 1x, at 48 by 48 for 2x, and at 72 by 72 for 3x. Vector files are different. Figma exports SVG at 1x only, because the file already scales. Developers then set the real size in code.
Tip
Do not make a raster asset bigger after export to fix blur. Export it at the right scale from the start, because a small image stretched later will look soft.
How Should You Name and Optimize Files?
Keep one pattern
Every file should follow the same order: what it shows, which variant it is, and which format it uses. Consistent names let developers guess a file's location.
Mark the scale in the name
Without it, two files can look the same and be used by mistake.
Compress raster files
Smaller PNG and JPG files load faster and use less space in the product. Run them through a compressor before handoff, and check that the result still looks clean.
Prepare icons in advance
Whatever method the team uses, it should be written down.
Worked Example: A Shopping App Product Page
Imagine a shopping app's product page. It has a cart icon, a brand logo, and several product photos. Each asset needs a different format. The steps below show how the design team decides and exports them.
- 1
Sort the assets by content
The cart icon and the brand logo are made of simple shapes. The product photos are real photographs with rich color and detail. That split decides the family for each asset.
- 2
Export the cart icon as SVG
The icon is a shape, so SVG is the right file. It stays crisp on a small phone and on a large tablet. Export it once, because SVG does not need separate scale files. Developers size it in code.
- 3
Export the brand logo as SVG
The logo is also a shape-based asset, so SVG keeps its edges sharp on every screen.
- 4
Export the product photos as JPG at 1x and 2x
Photos have no need for see-through areas, but WebP gives a smaller file than JPG. Export each photo at 1x for standard screens and at 2x for high-density screens. Compress each file so it loads quickly.
- 5
Add a JPG fallback
Some browsers or tools may not open WebP. Export the same photos as JPG at the same two sizes, and list them as the backup in the handoff note.
- 6
Name and document the set
Use one name pattern, such as the product name, then the scale suffix, then the format. Write down that the photos are WebP with a JPG backup, and that the icon and logo are SVG. The developer now has one clear set to build from.
Tip
In a real team, the export steps are repeated for every product page. A saved export setting on each asset saves time and keeps the files the same.
Common Mistakes to Avoid
Using PNG for every icon
A PNG icon has to be exported at several sizes, and it can look soft when stretched. An SVG icon covers all sizes with one file.
Using JPG for anything see-through
JPG has no transparency, so the background becomes a solid color. Use PNG or WebP when the asset must sit over other colors.
Exporting at 1x for every screen
A 1x raster file can look blurry on high-density screens. Add a 2x or 3x version for raster assets that people will see up close.
Sending files without notes
If the handoff lacks a format list and a reason for each choice, developers will guess. Write the set down and keep it with the assets.
Check Your Understanding
Your team needs to ship 40 navigation icons. They must look sharp on a phone and on a large desktop monitor, and their color must change for dark mode. Think about how each format handles size and color before you answer.
Quick check
Which format should the team choose for the 40 navigation icons, and why?
A team is preparing a large photo of a bakery counter for the home page. The photo has no see-through areas. The team wants the smallest file, with a backup for older browsers.
Quick check
Which pair of formats fits this photo best?
A designer must export a settings screen for the documentation site. The screen has small gray labels and a soft shadow, and it sits over a colored background.
Quick check
Which format should the designer use for this screen?
Key Takeaways
A design system needs a standard set of file formats, not a different choice for each designer. Use SVG for icons, logos, and simple illustrations, because they stay sharp at any size. Use PNG when you need transparency or sharp text, JPG for photos without transparency, and WebP or AVIF as smaller modern options with a backup. Export raster files at the right scale, name them the same way every time, and write the set down for developers.
Tip
Before you hand off an asset, ask three questions: is it a shape or a photo, does it need see-through areas, and does the handoff note name the format and the backup? If you can answer all three, the asset is ready.
Sources
- Figma Help Center: Export formats and settings for static designs
- DesignSystems.com: A complete guide to iconography (Bonnie Kate Wolf)
- Adobe Express: How to Choose the Right Image Format Every Time
- BlazingCDN: Best Image Format for the Web: JPEG, PNG, WebP, AVIF, SVG
- Orquitool: Choose the Right Image Format (PNG, JPG, WebP, SVG, AVIF)
- Figma Plugins guide: How to Export From Figma: PNG, JPG, SVG and PDF
- Figma Plugins guide: Figma Export Blurry? How to Export High Quality PNG and JPG
- Learn Figma for UX: 34. Export Individual Assets
- MadeVisual Studio: Brand asset file formats: a working guide
- MadeVisual Studio: Brand asset handoff checklist for developers
- Peasy Image: Batch Exporting Design Assets for Developer Handoff
- Figma Community Forum: Every icon best practice you need to know
- Edurev: Exporting Assets - Complete Web and Mobile Designer UI/UX
- Digital Sauce: How to Export SVG to PNG at High Resolution (2x, 3x, 4x)
- SVGMaker: SVG vs Raster Images: Complete Format Comparison Guide
- DoItSwift: Best Image Format for Websites in 2026: WebP vs AVIF vs JPG vs PNG
Last updated on 17 November 2026
Related lessons
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.