How to download a crypto logo as SVG

Search for "ethereum logo svg" and you get a mix of official files, redrawn copies, outdated versions and PNGs wrapped in .svg files. Some of them look fine in a thumbnail and fall apart the moment you scale them up.

This guide covers where good logo files come from, how to confirm that a file is a real vector, and what to check before it goes into a product, a slide or a print job.

Where crypto logos come from

There are three common sources, and they serve different purposes.

If you need the exact brand mark, for a co-marketing page or a printed banner, start with the project's own press kit. The guide on press kits and brand guidelines explains where those usually live and what they contain.

For product interfaces, an icon library is usually the better fit. A balances list with 40 tokens looks uneven when every logo was exported by a different team at a different size and padding. A library that redraws marks onto one grid gives you consistent sizing out of the box.

Token lists are built for apps, not for designers. The token lists and logoURI guide covers how they work, but in short, treat a logoURI as something to display, not as source artwork.

Downloading from Web3 Icons

The icon library has more than 2,000 logos for tokens, networks, wallets and exchanges. To get a file:

1. Search by name, ticker or an alternative name. Typing Sepolia finds the Ethereum network logo, because testnets share their mainnet's logo. You can also filter by category, for example tokens only or networks only.
2. Pick a style: branded, mono or background. If a logo has no mono version yet, the branded one is shown instead.
3. For mono, pick a color.
4. Pick an export size: 16, 24, 32, 48, 64, 128 or 256 px.
5. Download the SVG, or copy the SVG code to paste straight into a design tool or a code editor.

The export size sets the width and height attributes on the <svg> element. The viewBox stays the same, so the drawing still scales cleanly if you resize it later. Each icon page, such as Ethereum or USDC, also lists the colors used in the logo.

The artwork comes from the open source web3icons library under the MIT license. The logos themselves remain trademarks of their owners, which matters more for marketing use than for showing a token next to its balance.

Is it really a vector?

An SVG file can contain anything, including a raster image. Some sites export a PNG, wrap it in an <svg> element and call it a vector. It looks like this inside:

<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512">
  <image width="512" height="512" href="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAA..." />
</svg>

That file will blur when scaled, can't be recolored, and is often much larger than a real vector. A genuine icon is made of shapes:

<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24">
  <path fill="#3D4A66" d="M12 3v6.65l5.63 2.52z" />
  <path fill="#3D4A66" fill-opacity=".6" d="m12 3-5.63 9.17L12 9.65z" />
</svg>

Three quick checks catch most problems:

• Open it in a text editor. Look for <path>, <circle>, <rect> and <polygon>. If you find <image with a data:image/png or data:image/jpeg value, the file is a bitmap in disguise.
• Zoom in. Open the file in a browser and zoom to 400% or more. Vector edges stay sharp; embedded bitmaps turn soft or blocky.
• Look at the file size. A single-color icon is often under 2 KB and a detailed full-color one rarely needs more than 10 to 20 KB. A simple mark weighing hundreds of kilobytes is either hiding a bitmap or carrying far more points than it needs.

Choosing a style and a size

Most crypto logos are useful in three styles. Branded is the full-color mark and is the default for token lists, market tables and anywhere the logo identifies an asset. Mono is a single color you can change, which suits navigation, dense tables, dark slides and one-color print. Background puts the mark on its own colored tile, which keeps it readable on busy or unpredictable backgrounds. The branded, mono and background guide goes into when each one fits.

Size matters less for SVG than for PNG, because the file scales. It still matters in two ways. Design tools and slide apps import the file at its stated width and height, so picking a size near the one you will use saves resizing. And some logos are drawn with detail that only reads at larger sizes, so if you plan to show a logo at 16 px, look at it at 16 px before committing.

Verify the file before you use it

A few minutes of checking prevents most of the problems that show up later:

• The root <svg> has a viewBox. Without it, the drawing will not scale with the element.
• There is no <image> element hiding a bitmap.
• There is no <script>, no on... event attribute and no external reference you don't expect. This matters most if you will paste the SVG inline into a page; the SVG security guide explains why.
• If you plan to place many icons inline on one page, check whether the file uses id attributes for gradients or clip paths. Duplicate IDs can make gradients vanish when the same icon appears twice.
• It is the logo you meant. Wrapped and bridged versions of a token can have their own marks, and a network's testnet often uses the mainnet logo, so the label next to it has to do the distinguishing.
• It reads on the backgrounds you will use. A black or very dark mark that looks fine on white can disappear on a dark theme.

If all of that passes, you have a file you can resize, recolor (for mono) and convert to PNG later without going back to search.