Logo File Formats & Color Systems

    Logo File Formats Explained: SVG, PNG, EPS, PDF When to Use Each

    Chris Merriam
    Jun 20, 2026
    20 min read
    12 views

    A plain-English guide to logo file types, what each format is for, when to use it, and how to stop sending the wrong one. SVG, PNG, EPS, PDF, JPG, and the new web format

    You ever get an email like this?

    > "Hey can you send me the logo? Just a quick one for the deck."

    And then twenty minutes later, a second email:

    > "Sorry, the one you sent has a white box around it. Can you send a different version?"

    And then, an hour after that, a third:

    > "Actually our printer says they need 'vector.' Do you have that?"

    Same logo. Three different formats. One increasingly irritated request thread. This is the logo file format problem in its natural habitat, and almost every brand stumbles into it because nobody ever sat them down and explained which file does what.

    So let's do that now. By the end of this you'll know exactly what to send when someone asks for "the logo," and (maybe more importantly) what to push back on when someone asks for the wrong thing.

    TL;DR

    For the web: SVG first. WebP as a modern raster fallback. PNG as the universal raster fallback.

    For print: PDF first, EPS second. Both in CMYK if you have them.

    For slide decks, social media, and email: PNG with a transparent background. Three sizes (~400px, ~1000px, ~2000px) will cover almost everything.

    For your designer's archive: the AI file. Don't send this to anyone else.

    Never use JPG for a logo unless the "logo" is actually a photograph of a logo on a physical object. It can't have a transparent background and the compression chews up sharp edges.

    Now the longer version, because the cheat sheet doesn't tell you why, and the why is what stops you from making expensive mistakes.

    The cheat sheet (steal this)

    Format Type Best for Avoid for Transparent background?
    SVG Vector Websites, apps, modern email signatures Print shops still on legacy software Yes
    PNG Raster Slide decks, social media, anywhere needing a transparent background on screen Large print jobs, anything that will be resized way up Yes
    JPG Raster Photographs, hero images Almost any logo use No
    PDF Both Sending to printers, sharing with non-designers, brand guidelines Embedding in code or a web page Yes
    EPS Vector Embroiderers, sign makers, old-school printers Web, modern design tools, anyone under 35 Yes
    AI Vector (source) Archive only. Your designer's working file. Sending to literally anyone else Yes
    WebP Raster Web (faster than PNG) Print, email, anything offline Yes

    Print that out. Tape it to your monitor. That table answers most of the "best file type for logo" questions you'll ever have.

    Vector vs raster (this one paragraph matters)

    There are two fundamental kinds of image files, and every logo format is one or the other.

    Vector files store the logo as math. Points, curves, fills. They scale to any size without losing quality. A vector logo can be a 12-pixel favicon or a fifty-foot truck wrap, same file, no blur. SVG, EPS, AI, and PDF (mostly) are vector formats.

    Raster files store the logo as a grid of colored pixels. They have a fixed resolution. Blow them up past their native size and you get the soft, blocky mess that makes a brand look amateur. PNG, JPG, and WebP are raster formats.

    The single biggest logo file mistake people make is using a raster file where they needed vector, usually because the raster was the only one they could find. If you take nothing else from this article, take this: for anything being printed, resized, or projected, you need a vector file. If your master logo is a PNG, you don't have a logo. You have a snapshot of one.

    SVG: the web's native logo format

    SVG stands for Scalable Vector Graphics. It is, hands down, the right format for displaying your logo on the internet in 2026.

    A few things make SVG special.

    It's vector, so it stays crisp on every screen size and pixel density. Retina, 4K, the foldable phone screen someone insists on using to view your site.

    It's tiny. A clean SVG logo is often under 5KB. The same logo as a PNG suitable for the same display sizes might be 50KB or more. Multiply that across a site with the logo in the header, footer, favicon, and Open Graph image, and you're trimming meaningful page weight.

    It's text under the hood. An SVG file is XML. You can literally open one in a text editor and read it. This means you can change colors with CSS, animate it, make individual parts interactive, and (importantly for SEO) Google can read whatever text is inside. Wordmark logos in SVG are theoretically indexable in a way that PNGs never are.

    Where SVG falls apart: email. Outlook in particular is famously bad at rendering SVG, and a lot of corporate email clients strip or mangle them. For email signatures and email marketing, you still want PNG. We'll come back to this.

    Also worth knowing: SVGs can be a security concern if you accept user-uploaded ones, because that XML can contain scripts. If you're a developer reading this, sanitize your SVGs. If you're not, this never affects you.

    PNG: the raster workhorse

    PNG (Portable Network Graphics) is the format you'll use more than any other in day-to-day work, and it deserves a bit of respect even though it's the unglamorous one in the lineup.

    PNG's killer feature is transparency. Unlike JPG, a PNG can have a fully transparent background, which is why your logo doesn't show up in a white rectangle when you drop it onto a colored slide. This single property is why PNG won the logo-on-screen wars.

    PNG is also lossless. When you save a PNG, you don't lose detail to compression artifacts the way you do with JPG. The trade-off is bigger file sizes, but for logos (which are usually simple shapes with flat colors) PNGs compress remarkably well.

    When to reach for a PNG:

    • Slide decks. PowerPoint and Keynote both like PNG. SVG support in slides is technically improving but still inconsistent.
    • Email signatures and email marketing. SVG doesn't render reliably in email, so PNG is the safe choice.
    • Social media uploads. Most platforms convert whatever you upload anyway, but starting with a high-quality PNG with transparency is the right move.
    • Document templates. Word, Pages, Google Docs. PNG is the lingua franca.
    • Any time you need transparency on screen but can't use SVG.

    You usually want a few PNG sizes prepared in advance: a small one (around 400px wide) for email and signatures, a medium one (around 1000px wide) for slides and documents, and a larger one (2000px+ wide) for retina-quality display. Bigger isn't always better. A 4000px PNG in your email signature is a slow-loading mistake.

    A specific PNG gotcha: people often save PNGs with a checkerboard pattern visible, thinking that's the background. The checkerboard means transparent. It's how design software shows you "no background here." If your logo PNG shows up with a checkerboard in Preview, that's good, not a problem.

    Quick and important: JPG (sometimes JPEG) is a raster format designed for photographs. It uses lossy compression that's tuned for complex, gradient-heavy images. It cannot have a transparent background. Ever.

    For logos, this is almost always wrong. A JPG logo dropped onto any non-white surface shows up inside a glaring white rectangle. The compression also chews up the sharp edges of typography and clean shapes, leaving a smudgy halo around the logo when you zoom in.

    If you only have your logo as a JPG, your logo is in trouble. Find the original, talk to your designer, or get someone to vectorize it for you. Do not just keep using the JPG and hope nobody notices the white box on the dark blue email banner.

    The one place JPG is fine: a flat photo of your logo on a physical object (signage, packaging photography). That's a photograph of a logo, which is different from a logo file.

    PDF: the universal translator

    PDF is the most underrated logo format. It does almost everything reasonably well, and a lot of professionals just default to PDF for delivery because it cuts through compatibility issues.

    A PDF can contain vector art (so it scales without losing quality), embedded fonts (so the typography stays correct on systems that don't have your font installed), and transparency (which old EPS files struggle with). It opens on basically any device. Your grandparents can open a PDF. Your printer can open a PDF. Microsoft Word can place a PDF.

    When PDF is the right call:

    • Sending the logo to a printer. Most modern print shops actually prefer PDF over EPS these days. It handles modern design features more gracefully and they don't have to wrestle with font issues.
    • Sharing brand guidelines. A PDF brand guide with logos embedded is portable and consistent across viewers.
    • Sending the logo to someone non-technical. You can email a PDF logo and reasonably expect them to be able to open it, print it, and place it in a Word doc without any drama.
    • Archiving a "delivery copy" of your logo. A vector PDF is a safe long-term format.

    One pro-level note: for serious print work, ask your designer for a PDF/X export specifically (PDF/X-1a or PDF/X-4). It's a print-safe subset of PDF that flattens transparency, embeds fonts, and locks in color profiles. Print shops love it. You don't need to know the difference; you just need to know to ask.

    Where PDF struggles: you can't embed it in a webpage as an image. You can't use it as an avatar on social media. It's a delivery and document format, not a display format.

    EPS: print's grumpy uncle

    EPS (Encapsulated PostScript) is old. It came out in 1987. It has stuck around for nearly four decades because the print industry decided it works, and the print industry changes its mind approximately once per geological era.

    In 2026, EPS matters in specific places:

    • Embroidery shops. Their machines and conversion software often expect EPS.
    • Sign makers and large-format printers. Especially independent shops with mature workflows.
    • Promotional product vendors. The companies that make your branded mugs, pens, tote bags. They want EPS.
    • Screen printers. The t-shirt and merch crowd.

    If someone says "we need the vector file" and they're producing a physical object, EPS is the safe send. Even better: send both EPS and PDF, and let them pick.

    EPS's weakness is transparency and modern effects. It was designed before soft drop shadows and gradient meshes were a routine part of logo design. If your logo has fancy visual effects, an EPS export might flatten them or render them oddly. This is increasingly why PDF is eating EPS's lunch in modern print workflows. But EPS hasn't gone away, and won't for a while yet.

    Do not send EPS to:

    • Anyone using a web browser
    • Anyone in Figma
    • Anyone using Canva
    • Anyone who said "just send me a quick logo for my Instagram"

    AI: not really a logo file (a brief note)

    AI is Adobe Illustrator's working file format. It's not really a delivery format; it's a source format. Your designer works in AI. You archive the AI. You don't send AI files to clients, printers, or web developers.

    If your designer hands you only an AI file and nothing else, ask for exports: SVG, PNG, PDF, and EPS at minimum. That's a normal request, and any working designer will know exactly what you mean.

    WebP and AVIF: the new kids

    Two newer raster formats are worth knowing about, especially if you care about site performance.

    WebP is Google's modern image format. It supports transparency like PNG, compresses better than PNG, and has near-universal browser support in 2026. For web use, a WebP logo is often 25 to 35% smaller than the equivalent PNG. Most modern content management systems will auto-generate WebP versions from your uploads, so you may already be serving WebP without knowing it.

    AVIF is even newer and compresses better still, but support is more patchy and the encoding takes longer. For logos specifically (which are usually small files to begin with) the gains are marginal versus WebP. Worth knowing exists. Not worth losing sleep over.

    For most teams, the practical approach is: use SVG when you can, fall back to WebP for the web when you can't, and keep PNG around for everywhere else. If your developer wants to serve WebP, let them.

    Color space: RGB, CMYK, Pantone

    Logo files don't just carry shape. They carry color information, and the color space they're saved in changes how that color looks.

    RGB is for screens. Your SVG, your web PNG, your social media uploads. All RGB. The colors you specify show up roughly as you specified them.

    Within RGB, there are sub-profiles. The default is sRGB, which is what every browser and screen assumes. There's also Adobe RGB and Display P3, which can show a wider range of colors but only on specific hardware. Stick with sRGB for anything that will live on the web. The browser will assume sRGB anyway, and a file saved in Adobe RGB without the right tag can show up with washed-out colors.

    CMYK is for print. Inks mixing on paper behave differently than light on a screen, and a logo that looks vibrant in RGB can look weirdly muted in CMYK if it wasn't designed with print in mind. When you're sending files to a printer, CMYK PDFs or EPS files are what you want. If you only have RGB, the printer will convert. But the conversion may shift your colors in ways you don't love.

    The specific risk: brand colors that pop on screen (especially saturated blues, vivid greens, and electric oranges) often fall flat in CMYK. If your brand uses any of these, ask your designer to specify a CMYK equivalent in your brand guidelines so the print version doesn't surprise you.

    Pantone (PMS) is for when color accuracy matters at a level CMYK can't guarantee. Branded merch, packaging, anywhere your brand color absolutely must match across thousands of units. Pantone colors are specified by code (like "PMS 286") and printed using pre-mixed inks. If your brand guidelines don't include a Pantone equivalent for your primary color, ask your designer for one. The Pantone color matching system isn't free for designers to license anymore, which has gotten complicated, but the color codes themselves are still industry standard.

    Accessibility and logo files

    Most logo files aren't accessible by default, and most teams don't think about this until a screen reader user files a complaint or an audit fails.

    The fix is easier than you'd think.

    For SVG logos, you can embed accessibility metadata directly inside the file. A `` inside the SVG tag. Most designers don't include this by default. Ask for it.

    For raster logos (PNG, JPG, WebP) embedded in web pages, accessibility lives in the HTML `alt` attribute, not the file itself. The alt text should describe the logo for someone who can't see it. "Acme Co. logo" is fine. "Logo" alone isn't. You don't need to start with "image of" or "picture of" since screen readers already announce that.

    For PDFs, accessibility is its own large topic. The short version: a PDF used for brand delivery doesn't typically need to be tagged for accessibility, but a PDF used as the primary version of a public document does. Different problem, mostly outside the scope of this article.

    Transparency, naming, and other details

    A few more things nobody told you about logo files.

    Transparency is not free

    A transparent background sounds like a no-brainer, but it adds file size to a PNG and can complicate print workflows. For a logo that's only ever going on a white background, a JPG might actually be the more efficient choice (the only situation where I'd say this). For everything else, transparent PNG remains the default.

    File naming is half the battle

    The best file formats in the world are useless if nobody can find the right one. A folder called `Logos/` with twelve files named `logo_FINAL.png`, `logo_FINAL_2.png`, `logo_v3_FINAL_use_this.png` is a folder full of landmines. A folder with files named `acme-logo-primary-rgb.svg`, `acme-logo-primary-rgb-1000px.png`, `acme-logo-primary-cmyk.pdf` is a folder anyone can use.

    A workable convention:

    ```

    {brand}-{logo-name}-{variant}-{color-space}-{size}.{ext}

    ```

    Examples:

    • `acme-logo-primary-rgb.svg`
    • `acme-logo-primary-rgb-1000px.png`
    • `acme-logo-icon-reversed-rgb.svg`
    • `acme-logo-primary-cmyk.pdf`

    Build the naming convention once. Use it forever. Your future self will thank you.

    Common mistakes to avoid

    A short list of the format-related mistakes that show up most often in real brands.

    Using a JPG as your master logo. Once your logo only exists as a JPG, the original information is lost. You can't add transparency back. You can't recover sharp edges. Either find the vector source, or pay someone to vectorize the JPG and rebuild it. Don't just keep using the JPG and hope.

    Sending the AI file to a printer. Most printers can technically open AI files. Many will not appreciate it. PDF or EPS first, AI as a fallback only if they ask by name.

    Forgetting the reversed (white) version. Every brand needs a version of the logo that works on dark backgrounds. Usually a flat white version, sometimes a reversed-out version where the colors invert. If your brand kit doesn't include one, partners will improvise, and the improvisation will look bad.

    Letting PNG transparency get baked into white. Some export workflows (especially older ones in PowerPoint or Word) flatten transparent PNGs against a white background when you copy and paste. The result: your PNG looks transparent in the file but has a white box when used. The fix is usually to insert the file directly rather than copy-paste, but it's worth testing.

    Resizing a raster up. A 200px PNG resized to 2000px is not a 2000px image. It's a 200px image stretched to look bad at 2000px. If you need bigger, you need the vector.

    Storing the only good copy in one person's email. This is the slow-motion disaster nobody plans for. The original designer leaves. The email account gets archived. Three years later, someone realizes the only working AI file existed in an attachment from 2021. Don't let this happen.

    What to send to whom: the field guide

    When in doubt, here's who wants what.

    Your developer building the website: SVG. Maybe a PNG fallback. Maybe a WebP. They'll tell you.

    Your printer: PDF first, EPS second. Send both if you have them. Confirm color space (CMYK for print). Ask if they want PDF/X.

    Your embroidery vendor: EPS, plus a JPG or PNG reference of what it should look like.

    Your sign maker: EPS or vector PDF, CMYK or with Pantone callouts.

    Your team for slide decks: PNG with transparent background, around 1000px wide.

    Your email signature: PNG, around 400px wide. Not SVG.

    Your social media manager: PNG with transparent background, usually 1000 to 2000px. Some platforms want a 1:1 square version.

    Your CEO who texted "send the logo": PDF. Always PDF. PDF opens on everything and they won't have to ask follow-up questions.

    Your designer cousin who's "redesigning the website real quick": SVG, and a PDF of the brand guidelines so they don't do anything weird.

    A small closing thought

    Most of the logo file format anxiety in the world comes from a simple gap. Nobody set up a system where the right file is easy to find, and nobody documented which file is for what. So everyone defaults to "send the PNG" or "send the AI file" and hopes it works out.

    The fix isn't complicated, in theory. Maintain a small, clean set of exports for every logo: SVG, two or three PNG sizes, a PDF, and an EPS. Name them clearly. Store them somewhere that isn't a random Slack channel from 2022. Hand them out with a one-line note saying which one is for what.

    In practice, of course, that maintenance is exactly what nobody does, which is why brand portals (and tools like SendTheLogo) exist. But you don't need a tool to fix the underlying problem. A tidy folder beats no folder. The format wars are mostly a documentation problem in disguise.

    Pick your formats. Name them well. Store them somewhere durable. The increasingly irritated email thread at the top of this article never has to happen again.

    ---

    Frequently Asked Questions

    There isn't one. The best format depends on what you're doing with the logo. SVG for the web, PNG for slides and email, PDF for print delivery, EPS for older print vendors, AI for the designer's archive. You should have all of these on hand.

    What's the difference between vector and raster logo files?

    Vector files (SVG, EPS, AI, PDF) store the logo as mathematical instructions, so they scale to any size without losing quality. Raster files (PNG, JPG, WebP) store the logo as a grid of pixels and lose quality when you enlarge them past their native size. Your master logo should always be vector.

    Can I convert a PNG to a vector file?

    Not really. You can use auto-tracing tools to approximate the shapes, but the result is usually rough and unusable for a clean brand mark. If you only have a raster logo, the right move is to have a designer manually rebuild it as a vector. It typically costs less than people expect.

    What file format should I send to a printer?

    PDF first. EPS second if they specifically ask. Confirm the color space (almost always CMYK for print). For high-end print work, ask your designer for a PDF/X export.

    What's the best logo format for a website?

    SVG. It scales perfectly on any screen, loads fast, and search engines can read text inside it. If you need a raster fallback for an older browser, use WebP first and PNG as the universal fallback.

    What format should I use for a logo in an email signature?

    PNG, around 400px wide, with a transparent background. SVG doesn't render reliably across email clients (Outlook especially), so PNG is the safe choice.

    Only if you do meaningful amounts of print work, branded merchandise, or packaging where color accuracy is critical. For everyday digital and basic print use, CMYK is enough. Ask your designer to specify a Pantone equivalent in your brand guidelines if you don't already have one.

    What's the difference between SVG and PNG for logos?

    SVG is a vector format: infinitely scalable, tiny file size, ideal for the web. PNG is a raster format: fixed resolution, supports transparency, ideal for slides, social media, and email. Most logos should have both.