Skip to content

File formats

SVG vs PNG vs EPS vs PDF for logos: choose by use case

The right format starts with where the logo is going. Here is a decision guide for four common choices.

The short answer

Use SVG for scalable digital artwork where it is accepted, PNG for fixed-size images with transparency, and EPS or PDF when they match a printer’s or production team’s specification. Check the file’s actual contents and color settings: the extension alone does not prove that a logo is vector, CMYK or ready to print.

1. Start with the destination

Imagine four people asking for the same logo: a developer, an office manager, a social-media manager and a printer. They need different things from the file. Give each a usable asset and a short explanation rather than asking them to choose from an unexplained folder.

The examples below are starting points. The destination’s published upload rules and the production supplier’s written specification take priority.

Practical logo format choices
DestinationStart withCheck before delivery
Responsive websiteSVG if supportedRendering, bounds, embedded images and site support
Presentation or documentTransparent PNG; SVG where supportedVisible background, pixel size and behavior in the actual app
Platform or email uploadPNG or JPG as specifiedAccepted formats, file size and required dimensions
Printer requests CMYK EPSVerified CMYK EPSVector content, colors and production compatibility
Supplier requests PDFPDF to their specificationColor spaces, fonts, vector/raster content and requested standard

2. SVG: a useful digital vector format

SVG describes graphics in an XML-based format. It is a natural option for logos made from vector shapes on websites and interfaces because the geometry can scale with the placement. Transparency is supported, so a separate background does not have to be baked into the artwork.

There are two important qualifications. An SVG can contain embedded pixel images, and different receiving applications can interpret complex features differently. A photograph wrapped in an SVG is still a fixed-resolution photograph. Reopen the exported file and inspect effects, clipping and text.

For a web handoff, ask the developer whether SVG is accepted in the site’s upload or asset pipeline. Include a raster alternative if another destination needs it. Keep the editable original separately; the exported SVG should be treated as a delivery asset unless source editing is part of the agreement.

Further reading: MDN: SVG and image formats

3. PNG: predictable pixels and transparency

PNG is useful when someone needs a raster image with a transparent background. It has a defined pixel width and height, so choose those dimensions from the placement instead of assuming that a file called “high resolution” is suitable for everything.

For a fictional presentation, you might supply a 1200-pixel-wide transparent primary logo and a white version for dark slides. That is a project choice, not a standard size. Check that the presentation tool preserves the proportions and that the logo is sharp at the actual displayed size.

Increasing an existing small PNG’s dimensions does not recreate the original vector detail. Generate a larger raster export from the master artwork when you need more pixels. Keep an eye on padding: a 1200-pixel canvas with a tiny logo in the middle provides fewer useful logo pixels than the dimensions suggest.

4. EPS: send it when the workflow calls for it

EPS remains relevant in production workflows that request it. Treat the supplier’s request as a specification to check, including the intended color model and any limitations of its software. Do not choose EPS simply because its filename sounds more professional.

An EPS can contain vector information and raster content. Inspect the artwork itself. Ask whether the receiving workflow expects process CMYK or named spot colors, and confirm how effects and transparency should be handled. A flattened or converted result can look different from the original.

If the printer requested a specific CMYK EPS, send that clearly labeled file rather than a digital SVG renamed with a different extension. Changing an extension is not a conversion. Keep a record of the approved production settings for future reorders.

Further reading: Adobe: save artwork, including EPS

5. PDF: inspect the contents and purpose

PDF is a convenient format for sharing a viewable asset or a fixed-layout document. It can contain vector shapes, text and raster images. Those possibilities explain why two files ending in .pdf can behave very differently.

A logo PDF and a PDF Logo Guide also have different jobs. The first supplies artwork. The second explains how to use that artwork and may contain screenshots, example layouts and text. Sending the guide to a printer does not replace the requested production asset.

For print, ask the supplier which PDF preset or standard, color spaces and output profile it needs. Inspect the exported file against that request. Do not assume that an ordinary PDF export is CMYK, that every object remains vector, or that “print ready” describes every possible printing process.

Further reading: Adobe: Illustrator PDF options

6. Keep format, color and size separate

Three decisions are easy to mix up: the file format, the color setup and the dimensions. Writing them separately makes a request easier to check. “PNG, transparent, 600 pixels wide” is more useful than “web version.” “PDF using the printer’s agreed settings” is more useful than “print file.”

For digital artwork, use the color setup expected by the receiving workflow. For print, confirm the color values and profile with the supplier. A label such as RGB or CMYK in a folder name is helpful navigation, but it is not proof of the file’s contents.

In logopack.app, standard exports include SVG, PNG, JPG, WebP and CMYK EPS. Pro can add CMYK PDF logo files from supported solid-vector SVG artwork and a separate PDF Logo Guide. CMYK PDF export rejects raster images, gradients, patterns, filters, masks and blend effects instead of silently falling back to RGB. It does not supply a printer-specific output profile or PDF/X certification. The PDF Logo Guide is a separate RGB reference document. Inspect your own assets against the supplier’s requirements; a sample cannot certify every source logo or print job.

A clearer asset request
Website: primary SVG plus transparent PNG fallback
Slides: primary and white PNGs at agreed pixel widths
Print: EPS or PDF using the supplier’s written specification
Instructions: separate PDF guide explaining versions and usage

7. Verify one real file from every output type

Start with the format the recipient will use first. Place it in the actual website, document or production inspection tool. Check that it opens, looks right and meets the brief. Then repeat the relevant checks across the other variations.

Keep the package small enough to understand. More extensions do not automatically improve the handoff. If nobody needs a format, explain why it is omitted and preserve the master so a new export can be prepared later.

  • Does the recipient’s app accept the file?
  • Are the artwork and letterforms complete?
  • Are transparency and background intentional?
  • Are raster dimensions sufficient for this placement?
  • Are vector and color claims supported by inspection?
  • Does the filename make the intended use clear?

PUT IT INTO PRACTICE

Ready to prepare your pack?

logopack.app turns existing SVG artwork into an organized logo package. Preview your files, choose the available export options and check the result before handing it over.

Start with the logo pack generator, explore the sample ZIP, or compare the current plans.

Open generator
← All guidesSuggest a correction