Using crypto logos in slides and documents

Decks about crypto products are full of logos: the chains you support, the wallets you integrate, the exchanges that list your token. They are also where logos most often look bad. A blurry PNG pulled from a search result, a wordmark twice the height of its neighbors, a dark logo vanishing into a dark slide.

The fixes are mostly mechanical. Use vector files where the app supports them, export PNG at the right size where it doesn't, size logos by eye rather than by numbers, and check the exported PDF before sending.

What each app accepts

Support for SVG differs by app and by version, so the details below may shift. The test is always the same: insert the file, zoom in to 400%, and see whether the edges stay sharp.

PowerPoint inserts SVG through Insert, then Pictures, and keeps it as a vector. Right-click a placed SVG and choose Convert to Shape to edit its parts, which is useful for recoloring a mono logo, but don't do this to a branded logo; brand guidelines usually require the original colors. Very old PowerPoint versions don't understand SVG, which matters if your deck goes to people outside your organization.

Keynote has accepted PDF as a vector image for a long time, so converting an SVG to PDF in a design tool gives you a sharp result in any version. Recent versions also accept SVG directly.

Google Slides has historically accepted raster formats, such as PNG, JPEG and GIF, but not SVG. Use PNG there, and if a future update changes that, test that the result stays sharp in the downloaded PDF.

Documents follow similar rules. Word for Microsoft 365 handles SVG the way PowerPoint does, and Google Docs has the same historical limitation as Slides, so use PNG there.

When PNG is the better choice

Even where SVG works, PNG is sometimes the safer file:

• The deck will be opened in Google Slides, or by people on older Office versions.
• The logo uses gradients, masks or clip paths, and the app renders them slightly wrong. Compare the inserted logo against the original in a browser; if they differ, use PNG.
• Many people will edit the deck, and you want logos that can't be accidentally ungrouped or recolored.

Export PNG at two to three times the size the logo occupies on the slide. On a 1920 by 1080 slide, a chain logo shown at 120 px needs a file of at least 240 px, and 360 px is safer for high-density laptop screens and zooming. A 512 px square PNG with a transparent background covers almost any logo placement in a deck. The SVG to PNG guide covers export settings and how to check edges.

On Web3 Icons, every logo downloads as SVG, so you can convert it to a PNG of whatever size the slide needs without losing quality.

Sizing logos consistently

Equal numbers don't produce equal-looking logos. A solid circle and a thin, angular mark of the same height look like different sizes: the circle feels heavier and larger. Wide wordmarks set to the same height as square icons dominate the row.

Some practical rules:

• Use icons, not wordmarks, when you show many brands together. Square or circular marks are much easier to balance than text logos of different lengths.
• Give each icon the same square box, for example 120 by 120 px on a 1920 px slide, and center it in that box.
• Then adjust by eye. Shrink dense, solid marks by 5 to 10 percent and enlarge thin or open ones slightly until the row looks even. The optical balance guide explains why this works.
• Align on centers, and use your app's distribute tools so gaps are equal.

Icon libraries drawn on a shared grid save most of this work, because the marks were already balanced against each other when they were drawn.

Logo walls

A slide of supported chains, integrated wallets or partners is a grid problem. A few choices make the difference between tidy and noisy:

• One style for the whole wall. Mix branded and mono logos and the wall looks unfinished. All-branded walls work on white or light gray slides. On dark slides, an all-mono wall in white is calmer, and it avoids dark logos disappearing.
• One grid. Equal cells, equal gaps, logos centered in cells. Four to six columns fit a 16:9 slide comfortably.
• Labels when the audience may not know the brands. A name under each logo helps people outside crypto; for an expert audience, logos alone may be enough.
• A neutral order. Alphabetical order avoids implying a ranking you didn't mean.

Showing a company's logo on a slide can suggest a relationship. "Supported networks" is a factual statement; a slide titled "Partners" claims more, and may need the other side's agreement. The partner logo walls and marketing use guides cover this in more depth; neither is legal advice, and your organization's counsel is the right reference for specific cases.

Keeping logos sharp in exported PDFs

Most decks end up as PDFs, and that export is where quality is often lost.

Vector logos inserted as SVG or PDF usually stay vectors when PowerPoint or Keynote exports a PDF. Raster logos are a different story: apps can downsample images to save space.

• PowerPoint compresses images by default. In its options, under image size and quality, you can turn off compression for a file or raise the default resolution. Change this early: once an image has been compressed in a saved file, the lost detail doesn't come back, and you have to insert the original again.
• Keynote asks for an image quality level when exporting to PDF. Choose the highest setting for a deck that will be read on screens.
• Google Slides can only work with the image you uploaded, so start with a PNG large enough for the slide. A 64 px file stays blurry however the PDF is exported.

Then check the result. Open the exported PDF, zoom to 400% on the logo-heavy slides, and look at the edges. Vectors stay crisp at any zoom; a soft or stair-stepped edge points to a raster logo that needs a larger file. Check the dark slides as well, and look for a logo with a black mark that has quietly disappeared.