Here is how to save Discord emojis on PC not as WebP: open the emoji, right-click it, choose Open Link, then in the browser address bar change the file ending from .webp to .png for a static emoji or .gif for an animated one, and choose Save image as. Or save the .webp that Discord hands you and convert it to PNG, which keeps the transparent background a JPG would flatten.
The reason a plain right-click save always gives you a .webp is that Discord serves every emoji as WebP by design, the same pattern that makes WebP show up uninvited on plenty of other sites. If you want the background on the format itself, the guide to WebP and AVIF covers it. This page sticks to the emoji problem: the two routes that get you a real PNG, the one nuance nobody explains about why the URL trick works, and what animation costs you.
Why Does Discord Save Emojis as WebP?
Discord's client and content delivery network serve every emoji as WebP, no matter what format it was uploaded in, which is why the download lands as a .webp file. Emoji can be uploaded as JPEG, PNG, GIF, WebP, or AVIF, but Discord normalizes what it serves back for display and download (Discord Developer Portal, Emoji Resource). This is a deliberate performance choice, not a broken download.
Discord's own engineering team wrote up the reasoning: WebP gives them true alpha transparency, efficient animation encoding, and large size reductions across the app, and the format also lets them strip EXIF metadata cleanly on the way out (Discord, Modern Image Formats at Discord). For emoji specifically, transparency and small file size are exactly what you want in a picker that loads hundreds of tiny images at once. The tradeoff is the one you hit here: the file you save is WebP, and you wanted PNG.
So there is no setting to flip inside Discord that makes it hand you a PNG. The fix happens after the file leaves Discord, and there are two clean ways to do it.
How to Save Discord Emojis on PC Not as WebP, Step by Step
The fastest route never downloads a WebP at all. Discord's CDN can serve the same emoji in a different format if you ask its URL for one, so you change the format in the address bar before you save. The second route saves the .webp normally and converts it. Both routes save Discord emoji as PNG with the transparency intact; pick by whether the emoji moves.
| Your situation | Best route |
|---|---|
| A static emoji you want as PNG | Change the URL ending to .png, then Save image as |
| An animated emoji you want to keep moving | Change the URL ending to .gif, then Save image as |
| A .webp already sitting in your Downloads | Convert it to PNG with Paint, Preview, or our tool |
| A whole set of custom emoji at once | Save each, then batch-convert the folder |
Change the URL From .webp to .png (static emoji)
Post the emoji into any channel or open it in the emoji picker, right-click it, and choose Open Link. That opens the raw image from cdn.discordapp.com in a browser tab, and the address will usually end in something like .webp with a size query after it. Change that .webp to .png in the address bar and press Enter. The image reloads as a PNG. Now right-click the reloaded image and choose Save image as, and the file writes to disk as a real PNG with the transparent background preserved. This is the Discord emoji WebP to PNG path most people actually need, and it takes about ten seconds once you have done it once.
Change the URL From .webp to .gif (animated emoji)
Animated emoji are served as animated WebP, and Discord's CDN will re-serve them as GIF the same way. Open the animated emoji's link, change the ending from .webp to .gif in the address bar, press Enter, and Save image as. You get a moving GIF instead of a single frozen frame. Do not change an animated emoji to .png: PNG has no way to hold multiple frames, so you would keep one still image and drop the motion. Static emoji go to .png, animated emoji go to .gif.
Why the URL Trick Works but Renaming a File Does Not
This is the part no guide explains, and it is the whole reason the trick is reliable. Changing the extension in the cdn.discordapp.com URL is a fresh request to Discord's server, and the CDN re-encodes the image into the format you asked for before sending it back. You are not relabeling anything; you are asking for a different file and getting one.
Renaming a WebP you already downloaded does the opposite of nothing useful. A WebP file is a RIFF container whose first bytes read RIFF, then a size, then WEBP, and those bytes do not change when you rename emoji.webp to emoji.png (Google Developers, WebP). The file is still WebP inside; only the label lies. Strict apps that check the real signature reject it, and lax viewers that trust the name hide the problem until something downstream breaks. The URL swap converts; the rename only pretends to. Keep that distinction and you will never ship a mislabeled file.
If the URL Swap Does Not Reload as PNG
A few things trip up the URL trick, and each has a quick fix. If the address still ends in a query such as ?size=128 after the extension, leave the query alone and change only the .webp that sits right before the ?; the size parameter is fine, the format is the part that matters. If the tab shows the old WebP after you press Enter, the browser cached the previous request, so force a reload or paste the edited URL into a fresh tab. If Open Link is missing from the right-click menu, you are in the desktop app's shorter context menu, so open the same emoji in a browser tab where the full menu appears. And if you land on a page instead of a raw image, you opened the emoji's info rather than its link, so right-click again and choose Open Link specifically.
Convert Discord Emoji to PNG From a Saved File
If you already saved the .webp, or the URL trick is not available where you are, convert the file itself. A built-in app on Windows or Mac does this in three clicks with no download, and the transparent background survives because both PNG and WebP carry a full alpha channel.
Convert on Windows With Paint
Right-click the saved .webp file, choose Open with, then Paint. Paint has read and written WebP natively since 2023, so the emoji opens straight away (PCWorld, Convert WebP to JPG or PNG). Go to File, then Save as, and pick PNG from the file-type list. Name it and save. If Paint does not offer WebP, Windows itself is behind rather than the file being broken; running Windows Update fixes most of those cases.
Convert on Mac With Preview
Double-click the .webp to open it in Preview, or right-click and choose Open With, then Preview. Go to File, then Export, set the Format menu to PNG, and save. There is no quality slider to worry about, because PNG output is lossless: what the WebP held, the PNG keeps, pixel for pixel.
Convert With Our Tool, No Install
Drop the saved emoji into the WebP to PNG converter, which already has PNG set as the output, and download the result. There is no install and no signup for files up to 25 MB, and batches up to 30 images at once, so a whole custom-emoji set converts in one pass instead of one file at a time. Every alpha pixel carries over exactly, since PNG is lossless and the tool writes back the pixels it read. A free account raises the batch to 100 images a month with a usage dashboard, and Pro is 12 dollars a month flat for 10,000 images, files up to 50 MB, and batches of 100. The metadata block a file might carry gets stripped as the image is rewritten.
Why PNG and Not JPG for an Emoji?
Choose PNG because JPG has no alpha channel, so a transparent emoji background fills with a solid color, almost always white, the instant you save it as JPG. That defeats the point of grabbing the emoji for a sticker, a status, or a chat overlay: a white or black box around the character looks broken wherever you drop it. PNG and WebP both store transparency; JPG never could.
The cost of keeping transparency is smaller than it looks. Take a standard 128 by 128 pixel emoji. Raw color alone needs 3 bytes per pixel for red, green, and blue, which is 49,152 bytes before any compression. Adding the alpha channel that stores transparency makes it 4 bytes per pixel, or 65,536 bytes, a one-third increase in raw pixel data. Both PNG and WebP compress that down hard afterward; the point is only that the fourth channel is cheap, and it is the channel that keeps your emoji see-through.
| Pixel data, 128 by 128 emoji | Raw bytes |
|---|---|
| RGB, no transparency | 49,152 |
| RGBA, keeps transparency | 65,536 |
The one time JPG is fine is when the emoji is going onto a solid background anyway and nothing transparent is at stake. In every other case, PNG is the right target.
| What you are saving | Save as PNG? |
|---|---|
| A standard emoji with a transparent background | Yes, PNG keeps every transparent pixel |
| A screenshot of a reaction bar where the background matters | Yes |
| An emoji you will paste onto a solid color anyway | JPG is fine, nothing transparent to lose |
| An animated emoji | Neither, use GIF, see below |
What Happens to Animated Emojis?
Converting an animated Discord emoji to a static PNG keeps one frame and drops the motion, no matter which converter does the work. Animated emoji are served as animated WebP, fetched with an ?animated=true marker on the URL rather than the plain link a static emoji uses, and a standard PNG has no format to hold the extra frames.
If the animation is the reason you wanted the file, keep it as WebP or convert it to GIF instead, either with the URL swap to .gif above or a dedicated GIF converter. A GIF holds every frame; a PNG holds one. There is no setting that squeezes an animation into a still format without losing what makes it an animation, so decide up front whether you want the motion or a clean single-frame image, and pick the format that matches.
Saving Emojis on Mobile and the Re-Upload Size Cap
On a phone, the right-click and URL-swap steps are limited, because the mobile app does not expose the same Open Link and Save image as menu that desktop and desktop browsers do. If a phone is all you have, open Discord in a mobile browser tab instead of the app and the URL trick becomes available again, or handle the save later at a computer.
One reason people grab an emoji as PNG or GIF in the first place is to re-upload it to another server. Discord enforces a small size cap on custom emoji, so an emoji you pulled and then edited can bounce back if it grew too large during editing. If yours will not upload, compress it first: a trimmed PNG or GIF goes through where the oversized original stalls.
When Not to Convert a Discord Emoji
Converting is the wrong move in a few cases, and knowing them saves you a step. If you are pulling an emoji only to re-upload it to another Discord server, keep it as WebP: Discord accepts WebP uploads directly, so converting to PNG first just makes a larger file for no gain. If the emoji is animated and the motion matters, do not force it into a still PNG at all; go to GIF and keep the frames. And if your goal is the smallest possible file, WebP is already smaller than the PNG you would convert it to, typically 25 to 35 percent smaller at the same visual quality, so converting trades size for compatibility rather than saving space.
Convert when you specifically need PNG: a design tool that refuses WebP, a sticker workflow that expects PNG, or a transparent asset you will drop onto other artwork. Match the format to where the file is going, and you sidestep both the flattened-background trap and the pointless-conversion one. When in doubt for a still emoji, PNG is the safe target, because it opens everywhere and holds the transparency.