Brand asset file formats: a working guide to the right files for every deliverable

Brand asset file formats: choosing the right file for every deliverable

A client opens the folder you sent and sees thirty files: .ai, .svg, .png, .pdf, .eps, .webp, and a handful of MP4s. Within a minute, they email back asking which one to use on a trade-show banner, which one their printer needs, and which one their developer should drop into the website header. That confusion is not a client problem. It is a packaging problem, and it is almost always caused by inconsistent brand asset file formats.

This guide is written for studios, in-house brand teams, and freelance designers who need a clear, repeatable system for naming, exporting, and delivering brand assets. It is not a software tutorial and it does not promote any single tool. The goal is practical: by the end, you should know which format to send in which situation, how to structure your folders, and how to write a short delivery note that prevents the most common asset-handling mistakes.

Why brand asset file formats matter more than most teams realize

A brand identity is only as useful as the assets a team can actually open. A logo file that the marketing team cannot open in PowerPoint is functionally useless. A typeface that arrives as a flattened PDF is dead to a developer. A motion bumper that exports as a 2 GB ProRes file will not make it through the web team’s upload form. The choice of brand asset file formats quietly decides whether a brand can be applied at all, or whether it lives only on the original designer’s hard drive.

Most brand guidelines focus on colors, type, and tone of voice. Far fewer explain the file layer underneath those decisions: which vector source to keep, which raster export to share, which print-ready PDF profile to use, and which video spec to hand off to social editors. When the file layer is unclear, three predictable problems appear.

• Version drift. The team uses a 2019 export of the logo because nobody knows a newer file exists. New campaigns are built on outdated assets, and the brand slowly fragments across touchpoints.
• Misuse of raster files. Marketers stretch a small PNG on a billboard, or use a screen-resolution JPG on a printed brochure, and the result looks amateur even though the original design was careful.
• Vendor friction. Print shops, signage companies, and developers all ask for different file types. Without a clear delivery system, every project turns into a back-and-forth email about attachments.

A small upfront investment in standardizing brand asset file formats prevents all three. The rest of this guide explains the formats themselves, the situations they fit, and the packaging conventions that make them usable by non-designers.

The core brand asset file formats, and what each one is for

Every brand library can be described with a small set of file categories. The names below are the ones most teams use in delivery notes. They overlap in capability, but each has a clear job.

Vector source files: AI, EPS, CDR, and the open SVG

Vector files describe shapes as mathematical paths rather than pixels. That means they scale cleanly from a favicon to a building wrap. They are the editable, working source for any brand mark, icon, or illustrated element.

• AI is Adobe Illustrator’s native working file. It preserves layers, effects, and editable type. It is the right format for the in-house designer or partner studio that will continue to evolve the mark.
• EPS is an older PostScript-based vector format. It is widely accepted by print vendors, sign makers, and legacy software. It is a good interchange format even though most modern tooling prefers SVG or PDF.
• CDR is CorelDRAW’s native format. Some print and engraving houses still use Corel workflows, so a CDR copy can be useful in specialized supply chains.
• SVG is the open, web-native vector format. It is XML-based, supported by every modern browser, and can be styled with CSS or JavaScript. For logos, icons, and illustrations used online, SVG is the right choice wherever the design system supports it.

Most studios ship a pair: the editable working file (AI or CDR) plus an open interchange file (SVG or EPS). A common brand asset file formats rule is to never give a vendor the only copy of the editable master. If the AI file is lost, the brand mark is effectively lost with it.

Raster export files: PNG, JPG, WEBP, and TIFF

Raster files store images as a grid of pixels. They are the workhorse of brand delivery because almost every tool can open them. Their weakness is that they do not scale cleanly beyond their original resolution, so a JPG made for a web banner cannot be reused on a 3-meter trade-show panel.

• PNG supports transparency and lossless compression. It is the right choice for logos on color backgrounds, social profile images, app icons, and any asset that needs a clean cut-out.
• JPG uses lossy compression and does not support transparency. It is the right choice for photographs, full-bleed backgrounds, and any image where file size matters more than pixel-perfect edges.
• WEBP is a modern image format designed for the web. It supports both lossy and lossless compression and can include transparency. For websites, it typically delivers smaller files at equivalent visual quality compared with PNG or JPG, which improves page performance.
• TIFF is an uncompressed or lightly compressed raster format favored in print production. It preserves full color depth and is appropriate for high-end print files, especially when the output is large format or fine art.

When listing brand asset file formats in a delivery note, it helps to specify not only the extension but the export parameters. A “logo PNG” can mean a 200-pixel icon or a 4000-pixel master. Both are valid; they are simply different assets.

Document and print files: PDF

PDF is the most flexible asset format in a brand library because it can hold vector, raster, and type in a single, self-contained file. It is the standard for print-ready artwork, brand books, pitch decks, and downloadable fact sheets. Three PDF profiles are worth distinguishing.

• PDF/X is a print-industry standard with strict color and font rules. It is what most commercial printers want for a press-ready job.
• PDF/A is a long-term archival profile. It is the right format for a brand book that the client must be able to open reliably in ten years.
• Standard interactive PDF is a regular PDF with hyperlinks and bookmarks, useful for screen reading. It is not print-ready unless it was exported with print rules in mind.

Motion and audio brand assets: MP4, MOV, Lottie, MP3, and WAV

Brand systems increasingly include motion: logo stings, social bumpers, animated icons, and UI micro-interactions. Each of these needs a specific format.

• MP4 with H.264 video and AAC audio is the most widely compatible deliverable for social, web, and presentations.
• MOV from QuickTime or ProRes is a higher-fidelity master, useful for broadcast, cinema, and editorial.
• Lottie JSON is a vector-based animation format that runs natively on web and mobile. It is the right format for UI motion, loading states, and lightweight brand marks that need to scale.
• MP3 and WAV cover audio brand assets such as sonic logos, podcast intros, and hold music. MP3 is the compressed delivery version; WAV is the studio master.

A practical map of brand asset file formats by use case

Format choice is not theoretical. It is a decision tied to a specific context. The table below maps common brand deliverables to the formats that usually work, with a short note on why each fits.

Deliverable	Primary format	Backup or alternate	Why this fits
Website header logo	SVG	PNG at 2x and 3x	SVG scales crisply on any screen and can be styled with CSS; PNG fallbacks cover older browsers and email.
Mobile app icon	PNG	SVG for adaptive icons	PNG is the required store format; SVG is helpful for Android adaptive layers.
Social profile image	PNG	JPG when file size is capped	PNG keeps edges clean on any platform’s circular crop.
Press kit photographs	JPG	TIFF for editorial print	JPG is small and compatible; TIFF is the master for magazine print.
Print brochure artwork	PDF/X	Open INDD or AI source	PDF/X is the printer’s contract; the source file is for future edits.
Outdoor banner or signage	Vector PDF or EPS	TIFF at 1:1 scale at final resolution	Sign makers prefer vector for large scale; TIFF is a fallback for raster-only shops.
Trade-show booth graphics	PDF/X-4	Layered AI source	PDF/X-4 supports transparency and layers, which most modern print pipelines expect.
Animated logo for social	MP4 (H.264)	GIF or Lottie for in-product	MP4 is universally accepted on social platforms; Lottie is for app and web UI.
Brand book	Interactive PDF (PDF/A for archive)	Web page version	PDF is portable and printable; a hosted page is easier to keep current.
Email signature logo	PNG	JPG for very small file size	Email clients do not render SVG reliably; PNG is the safest choice.
Sonic logo or audio sting	MP3	WAV master	MP3 is the universal delivery file; WAV is the master for studio reuse.

This table is a starting point. Real-world projects will adjust it. The important part is that the same decisions are made the same way every time, so that nobody has to re-derive the rule on a deadline.

How to choose between SVG, PNG, and PDF for a single logo

The logo is the asset that most often gets mis-delivered, so it is worth a closer look. Three formats cover almost every scenario, and the right choice depends on where the file will be used.

• Use SVG for the web and product UI. SVG is the only one of the three that stays crisp at any size, supports CSS recoloring, and can be animated or interacted with. It is the right default for any logo that lives on a website, in a design system, or in an application interface.
• Use PNG for compatibility and raster contexts. PNG handles transparency and works in email clients, slide decks, and social platforms that do not support SVG. It is also the right format for any context where a software limitation makes vector impractical.
• Use PDF for print and shared reference. A single-page PDF can hold a vector logo with embedded fonts and color profiles. It is a reliable format for sending a logo to a printer, a partner agency, or a legal team that needs an archivable copy.

A well-built logo package usually includes all three. The table below summarizes a typical logo set within a wider brand asset file formats system.

File	Format	Color mode	Typical size	Intended use
Logo primary, full color	SVG	RGB	Editable vector	Web, product UI, presentations
Logo primary, full color	PNG	RGB	2000 px wide	Slide decks, email, social, fallback raster
Logo primary, full color	PDF	CMYK	Vector	Print, partner agencies, archives
Logo monochrome	SVG	RGB	Editable vector	Single-color applications, embossing, dark mode
Logo reversed (white)	SVG and PNG	RGB	2000 px wide	Use on dark backgrounds and photography
Logo favicon	SVG and PNG	RGB	32, 48, 192 px	Browser tabs, bookmarks, app icons

Note the color mode column. Web assets should ship in RGB; print assets should ship in CMYK. Shipping a CMYK PNG to a web team is one of the most common brand asset file formats mistakes, and it produces dull, off-color results on screen.

Naming conventions that make brand asset file formats usable

Even a perfectly exported file becomes useless if nobody can find it. Naming and folder structure are part of the format decision, not separate from it. A few rules consistently help non-designers navigate a brand library.

• Use a stable file stem. The file name should describe the asset, not the export. acme-logo-primary.svg is stable; logo-v7-FINAL-from-mac.svg is not. Once the file is shared, the name should be safe to reuse across years.
• Put the format extension last. This sounds obvious, but it is worth enforcing. Browsers and operating systems sort by name, so acme-logo-primary.svg, acme-logo-primary.png, and acme-logo-primary.pdf sit together in any alphabetical list.
• Separate master assets from exports. The AI, INDD, or CDR working file is a master, not a deliverable. A simple folder split, such as 00-masters and 01-exports, signals to the client what they can edit and what they should treat as final.
• Group by asset type, not by project. /logos, /colors, /typography, /photography, /motion, /templates travel further than /launch-2025 or /rebrand-2026. A brand library outlasts any single campaign.

Export settings that decide whether a file is usable

Format choice is only half the answer. The export settings determine whether the file actually works in its target context. The checklist below covers the settings that most often go wrong inside brand asset file formats delivery.

Color profiles and mode

RGB for screen, CMYK for print, and a defined color space within each mode. For most brand work, sRGB is a safe default for screen assets, and either GRACoL or FOGRA39 is a reasonable starting point for coated and uncoated CMYK print. The exact profile depends on the printer, which is why a quick conversation with the print vendor is part of any large-format job.

Resolution

For on-screen raster, 72 to 150 ppi is enough. For print raster, 300 ppi at the final placement size is the standard. For very large format, such as building wraps, 100 to 150 ppi is often acceptable because viewing distance is greater. Writing the intended ppi into the file name or a README file removes ambiguity.

Transparency and matte

PNGs can carry an alpha channel. JPGs cannot. If a logo needs to sit on a colored background, send a PNG with transparency, not a JPG on white. The white matte in a JPG will appear as a white box on every dark background.

Type and outlines

When exporting a PDF or EPS for a vendor, either embed the fonts or convert the type to outlines. A PDF with a missing font is a common reason printers reject artwork. For internal editable sources, keep type live so the team can update copy without redrawing.

Video parameters

For social motion, square 1:1 at 1080 pixels and vertical 9:16 at 1080 pixels cover most platforms. For broadcast, follow the network’s delivery spec rather than designing your own. For UI motion, Lottie JSON is the right format because it scales without quality loss and keeps file size small.

Packaging and delivery: turning files into a usable brand library

Formats and naming are the substance, but packaging is what makes a brand library feel professional. Three small habits reliably improve the experience for non-designers.

• Write a short delivery note. A one-page PDF or README that explains the folder structure, the file naming pattern, and the most common use cases saves hours of email back-and-forth. It does not need to be polished; it just needs to be clear.
• Include a “start here” set. Most people will only ever use two or three assets. Curate a small folder of the most common files, named plainly, and link to the full library for the rest. The temptation to send the entire library at once usually slows people down rather than helping them.
• Version the library, not the files. When a logo changes, ship a new version of the whole library rather than dropping a replacement logo into an old folder. Versioning makes it obvious which set of files is current and which is archived.

If the library is hosted online, the same logic applies. A clear landing page, with the most-used files at the top and a search or filter for the long tail, will be used far more than a shared drive with hundreds of unnamed assets. For teams thinking about visual identity as a whole, the structural decisions around a visual identity system and the file formats that carry it are tightly connected, and both deserve a written standard.

Common mistakes when working with brand asset file formats

Even experienced teams make the same handful of errors. Watching for them in delivery reviews will save a lot of rework.

1. Sending a CMYK logo to a web team. A logo that looks fine in InDesign can look muted and orange on a website if it was exported in CMYK. The fix is simple: export a separate RGB version of the same logo for screen use.
2. Shipping a low-resolution PNG as the “master” logo. A 600-pixel PNG is fine for many uses, but it is not the master. The master is a vector file or a high-resolution PNG at the largest size the brand is likely to need.
3. Forgetting the reversed version. A full-color logo on a white background is only half of the system. A reversed, single-color version is needed for dark mode, photography, and packaging with strong color fields.
4. Using JPG for assets that need transparency. JPGs do not support an alpha channel. Any logo, icon, or illustration that needs to sit on a non-white background must be exported as PNG, WEBP, or SVG.
5. Mixing emoji and unicode icons into a “logo set”. Emoji and unicode glyphs are not part of a brand’s vector library. They render differently on every device and cannot be recolored with the rest of the system. Use SVG icons instead, and keep the brand mark clearly separated from UI icons.
6. Letting the folder structure drift over time. New campaigns create new folders, old folders linger, and within a year nobody can find the right file. A small annual review of the brand library prevents this.

How brand asset file formats connect to broader design system work

Format decisions do not live in isolation. They sit inside a larger design system that includes color tokens, type scales, component libraries, and motion principles. The file format layer is the part of the system that the rest of the company actually touches. A design system that defines colors as Figma variables but ships only flattened JPGs will be applied inconsistently, because the format layer quietly overrides the token layer.

Two practical guidelines help connect the two.

• Treat the asset library as a public product. The marketing team, the sales team, the partners, and the press are users of the brand library. Their experience of the brand often starts with downloading a file. A library that is hard to navigate will be worked around, and the workarounds will drift from the system.
• Document the format decisions in the brand book. A short page inside the brand book that lists which brand asset file formats to use, with examples, removes most of the guesswork from non-designers. The page does not need to explain the technicalities of vector graphics. It only needs to point people to the right file for the right job.

Putting it together: a simple brand asset file formats checklist

Before shipping a new brand library, or reviewing an existing one, the checklist below covers the most important decisions. It is short on purpose. The point is to make the same choices consistently, not to chase perfection on every export.

• Master vector source is saved in a stable, editable format (AI, INDD, or SVG), with type live and layers named.
• Open interchange copies exist in SVG for web and EPS or PDF for print.
• Raster exports are provided in PNG (with transparency) and JPG (without), with WEBP where the platform supports it.
• Color modes match the destination: RGB for screen, CMYK for print.
• Resolution is set for the use case: 72 to 150 ppi for screen, 300 ppi for print, 100 to 150 ppi for large format.
• Reversed, monochrome, and favicon variants are part of the logo set.
• File names use a stable stem, with the format extension last, and no version noise.
• Folder structure separates masters from exports and groups assets by type rather than by project.
• A short delivery note or README explains the structure and the most common use cases.
• Motion assets are exported at the resolutions each platform expects, with Lottie JSON for UI motion and MP4 for social.

Following this list does not require any particular tool. It only requires consistency, which is exactly what most brand libraries are missing.

Frequently asked questions

What are the most important brand asset file formats to deliver in a logo package?

A practical logo package should include a vector master (AI or SVG), a print-ready PDF or EPS, a high-resolution PNG with transparency, a smaller PNG for general use, and a reversed or monochrome version. This set covers websites, slide decks, email, social platforms, and most print vendors without further conversion.

Should I send SVG or PNG to a web developer?

Send SVG whenever the developer is comfortable with it. SVG scales without quality loss, supports CSS recoloring, and keeps file size small. Include a PNG fallback for email clients, very old browsers, or any context where SVG is blocked. The combination of SVG and PNG is the most reliable web delivery pair.

What is the difference between EPS and PDF for brand assets?

EPS is an older PostScript-based vector format, still supported by many print vendors and older software. PDF is a more modern, flexible container that can hold vector, raster, and type in a single file, and supports profiles such as PDF/X for print and PDF/A for archiving. For a new brand library, PDF is usually the better default, with EPS retained only when a specific vendor requires it.

What is the best brand asset file format for social media logos and icons?

PNG is the most reliable choice for social profile images, post graphics, and story assets because it supports transparency and is accepted by every platform. JPG is appropriate for photographic content. WEBP is a good alternative on platforms that support it, especially for web embeds where smaller file sizes improve loading times.

Do I really need a separate CMYK version of my logo?

Yes, if any of your brand applications are printed by a commercial press. CMYK and RGB render colors differently, and a logo that looks balanced on screen can shift noticeably in print. Keep an RGB version for digital and a CMYK version in PDF or EPS for print, and update them together when the brand changes.

How should I package brand assets for a non-designer client?

Group the assets by type (logos, colors, typography, photography, motion, templates) and place a small “start here” folder of the most common files at the top. Include a one-page delivery note that explains the folder structure, the file naming pattern, and the most common use cases. A simple structure is more valuable than a polished brand portal that nobody can navigate.

What format should motion brand assets be delivered in?

For social and web playback, MP4 with H.264 video and AAC audio is the most widely compatible choice. For UI and product motion, Lottie JSON is the right format because it scales without quality loss and keeps file size small. For broadcast or cinema, MOV or ProRes is the appropriate master, alongside the MP4 delivery version.

How often should a brand asset library be reviewed?

A light annual review is a healthy default. The review should check that the current logo files match the current guidelines, that no campaign-specific folder has drifted into the master library, and that the file naming convention is still being followed. Larger rebrands obviously trigger a full rebuild rather than a review.

Can I use a single file format for everything?

Not without tradeoffs. PDF is the closest thing to a universal brand asset format because it can hold vector, raster, and type, but it is not the right tool for web UI, social platforms, or motion. A small, consistent set of formats matched to clear use cases is more reliable than trying to force one format to do every job.

What is the fastest way to fix a brand library that has drifted?

Start by re-exporting the logo set from the most recent source file, in the formats listed earlier in this guide. Replace the old logo files across the library, then update the delivery note so the new structure is obvious. The rest of the asset cleanup can follow at a steadier pace, but the logo is the asset that most often defines how the brand is perceived, so it is worth fixing first.

Related reading

• Motion array basics: what it is and how creators use it
• Visual identity: what it is, what it includes, and how to build one