Paste Images to Download · Convert and Save Clipboard Content as Any Format

11 min read

Paste Images to Download · Convert and Save Clipboard Content as Any Format

The clipboard doesn't care about formats. When you copy an image — from a screenshot tool, a webpage, a chat app, or a photo viewer — your operating system stores it as a raw bitmap. The moment you want it as a file, you have to pick a format: PNG, JPG, WebP, AVIF. Each one is a different deal on file size vs quality vs compatibility.

This page is about the conversion step: how to paste an image from your clipboard and download it as the format you actually need, without installing any software.

The flow in one minute

  1. Open paste-to-download.com in any modern browser
  2. Paste with Ctrl+V (Windows / Linux) or ⌘+V (macOS)
  3. Pick your output format from the dropdown — PNG, JPG, WebP, or AVIF
  4. Click Download

The image is decoded by your browser, re-encoded to the chosen format, and offered as a download. No upload, no server, no signup. The whole thing takes one to two seconds.

For a longer walk-through of the basic clipboard workflow, see Paste to Download · Save Clipboard Images Instantly. This page is specifically about the format conversion decision.

The four formats, in 30 seconds each

PNG — the safe default

Lossless. Supports transparency. Bigger files than JPG for photos but smaller than uncompressed bitmaps. Universally supported (browsers since the 90s, every OS, every chat app).

Pick PNG when: the image has text, line art, UI screenshots, charts, diagrams, or anything where pixel-perfect fidelity matters. Also pick PNG when you need a transparent background.

Avoid PNG when: the file size matters and the image is photographic — PNG is 3-5× larger than JPG for the same photo at indistinguishable quality.

JPG — the photography format

Lossy. No transparency. Excellent compression for photos and natural images. Banding artifacts on gradients if you push the quality too low. Universally supported.

Pick JPG when: the image is a photograph, the file size matters, and you don't need transparency. Email attachments and most marketplace uploads also default to JPG.

Avoid JPG when: the image has crisp text, thin lines, or hard edges that JPG's frequency-domain compression smears. Also avoid for any image that might get re-saved multiple times — each save degrades quality.

WebP — modern default for the web

Lossless or lossy modes. Supports transparency. About 25-35% smaller than equivalent JPG / PNG. Supported in every modern browser since 2020 but not every chat app or email client handles it yet.

Pick WebP when: you're saving for a web page or a Slack-style chat app that supports it, file size matters, and you're confident the recipient's tools handle it.

Avoid WebP when: the file is going somewhere old-school (legacy CMS, MS Office documents, certain marketplaces) where compatibility hasn't caught up.

AVIF — the new heavyweight

Lossy with lossless option. Supports transparency. About 40-50% smaller than JPG at equivalent quality. Slower to encode than WebP but the file is smaller. Supported in browsers since 2022; still uneven in non-browser apps.

Pick AVIF when: you're building a website and serving images via <picture> with fallback, or sending to a recipient you know has modern tools. Best compression of the four.

Avoid AVIF when: you're not sure what the recipient supports. Encoding is also 3-5× slower than WebP, which adds a few seconds per image.

A simple decision rule

Most of the time:

  • For yourself or a known modern environment: WebP or AVIF
  • For sharing with someone (email, chat, marketplace): JPG for photos, PNG for everything else
  • For an unknown destination: PNG. It always works.

For a deeper comparison see PNG vs JPG vs WebP vs AVIF in 2026, which benchmarks each format on real images and shows the exact file size deltas.

The conversion is lossless if the source is lossless

A common worry: "if I paste a PNG and download as JPG, does it lose quality?"

Yes — JPG is lossy by definition. The first time you encode to JPG, quality drops to whatever the quality slider says (default is around 92, which is visually indistinguishable from lossless for photos).

But going to PNG, WebP-lossless, or AVIF-lossless is genuinely lossless. PNG → WebP-lossless → PNG → AVIF-lossless would not accumulate degradation, the same way zipping and unzipping a file doesn't change the bytes.

The practical rule: if you need to preserve the source exactly, use PNG (or WebP-lossless / AVIF-lossless if size matters). If file size matters more than pixel-perfect fidelity, JPG at quality 85-92 is the workhorse.

Compression alongside conversion

If the goal is just "smallest file that still looks good," pure format change is only half the answer. The other half is the quality knob. For that, the /compress tool combines both — paste an image, pick output format, drag a quality slider, watch the file size and visual quality update in real time.

The compress tool also supports a target file size mode — useful when an email gateway rejects attachments over 2 MB, or when a marketplace caps uploads at 500 KB. You set the target, the tool binary-searches the quality setting that hits it.

For a more detailed treatment of compression strategy, see How to compress images without losing quality and Compress PNG to under 100 KB.

What about HEIC?

If you copy an image from an iPhone Photos app (or AirDrop a .HEIC file to your Mac), the clipboard might contain HEIC. Some apps decode it on the fly when you paste; others leave it as HEIC.

The paste-to-download flow handles either case — the browser's image decoder reads HEIC via a WebAssembly library, and you can then re-encode as any of the four formats above. For batch HEIC files (rather than clipboard), /heic-to-jpg is the more direct tool.

For context on why iOS standardized on HEIC and when conversion matters, see Why iPhone uses HEIC and when to convert.

Common conversion scenarios

Slack screenshot → JPG for email

You screenshot a chart in Slack (which lands on your clipboard as a PNG). Your colleague needs it but their email gateway rejects PNG attachments over 1 MB. Paste-to-download, switch the format dropdown to JPG, quality 85, click download. The output is a 200 KB JPG that looks identical to the source for practical purposes.

Webpage image → WebP for a blog

You're writing a blog post and want to include a screenshot from a research paper. Right-click the image on the paper's webpage, copy. Paste-to-download, pick WebP, download. You get a small file that loads fast and looks great on modern browsers. (If you also need a PNG fallback for older readers, download twice.)

Phone photo → AVIF for archive

You took a photo on your phone, sent it to your Mac. You want the smallest archive size for long-term storage. Paste-to-download, AVIF lossless mode, click download. The file is roughly half the size of the original JPG with no quality loss.

Sketch / Figma export → PNG for a doc

You exported a design from Figma to clipboard. The design has transparent areas and crisp text. Paste-to-download, keep the format as PNG (the default), download. The transparency and text edges survive unchanged.

When to install software instead

The paste-to-download flow handles single-image conversion well. For bulk operations (thousands of images, integrated into a build process) command-line tools like ImageMagick, ffmpeg, or cwebp / avifenc are still the right answer.

For processing 10-100 images at a time though, the browser tools on this site let you drag a folder onto the page and they batch-process in parallel. The output is offered as a zip download.

FAQ

Can I paste an image and download it without converting? Yes. Pick the format that matches the source (PNG for a PNG screenshot, JPG for a JPG photo). The tool decodes and re-encodes, which is technically a round-trip, but losslessly if both ends are lossless formats.

Why is AVIF so much slower to encode? AVIF's compression algorithm does more work per pixel than JPG or WebP. On a typical laptop, AVIF encoding is 3-5× slower than WebP. The payoff is a 30-50% smaller file at the same visual quality.

Does the format affect EXIF metadata? Different formats handle EXIF differently. JPG and WebP preserve EXIF if the encoder is told to keep it; PNG technically supports metadata but most encoders strip it; AVIF preserves it. If privacy matters, run the output through /exif to inspect and strip metadata before sharing.

Can I batch-paste multiple images? The clipboard API exposes one image at a time. For batches, drag the files onto the tool page after pasting the first one — they queue up for processing.

Is there a quality difference between the same format from different tools? In principle, no — PNG is PNG, JPG is JPG. In practice, encoder libraries vary slightly. The browsers' built-in encoders (which paste-to-download uses) are well-tuned for typical use cases and produce output indistinguishable from Photoshop or GIMP at the same quality setting.

Where to go next

If you want the simplest possible paste-and-download flow without thinking about formats, paste-to-download.com just works — defaults to PNG, click download, done.

If you want to also resize, crop, or remove the background while you're at it, the tools menu covers all the common operations.

For format-specific deep dives: