How to Compress Images for Social Media Without Losing Quality

Updated May 2026

Why your uploads look blurry - and how to fix it before the platform's algorithm makes things worse

You spent time getting the aspect ratio right. You exported at the correct pixel dimensions. But after uploading to Instagram or Facebook, the image looks softer, colors are slightly off, and fine details have turned to mush. Sound familiar?

The problem isn't your camera or your design software. Every social media platform re-compresses your images after upload. Facebook, Instagram, Twitter/X, LinkedIn - they all run your files through their own compression pipeline, regardless of what format or quality level you uploaded at. The goal is to save bandwidth and storage, and your image quality pays the price.

But here's the thing: how much quality you lose depends heavily on what you upload. If you hand a platform a bloated 15 MB file, it has to compress aggressively. If you give it a lean, properly compressed file that's already close to the platform's target size, the re-compression is minimal. This guide shows you exactly how to prepare your images so platforms have as little reason as possible to degrade them further.

Why Every Platform Compresses Your Images

Think about the numbers. Instagram processes over 100 million photos per day. Facebook handles even more. If every image stayed at its original 8 MB file size, the storage and bandwidth costs would be astronomical. So platforms compress everything.

The compression happens server-side after your upload completes. You can't opt out of it. But not all compression is equal - some platforms are more aggressive than others, and the amount of compression applied depends on the file you submit.

The Re-Compression Problem

If you export a JPG at 80% quality, then the platform compresses it again at its own quality level, you get double compression. Each round of lossy compression introduces new artifacts. The text gets fuzzier, gradients develop banding, and edges lose sharpness. This is why uploading a "good enough" JPG often produces worse results than uploading a high-quality source file at the right size.

Platform File Size Limits

Every platform has a maximum file size for uploads. Stay under the limit or your upload will fail - but staying well under the limit is actually the smarter move. When your file size is close to the platform's target output size, the re-compression pass has less work to do.

Platform	Max File Size	Recommended Upload Size	Notes
Facebook	30 MB	1-3 MB	PNG under 1 MB may avoid re-compression
Instagram	30 MB	1-2 MB	Aggressive compression on photos over 1 MB
Twitter/X	5 MB (mobile) / 15 MB (desktop)	1-3 MB	PNG under 900 KB stays lossless
LinkedIn	10 MB	1-2 MB	Heavy compression on feed images
Pinterest	20 MB	2-5 MB	Less aggressive, keeps more detail
Discord	25 MB (Nitro: 50 MB)	2-8 MB	Minimal re-compression on most images
Telegram	10 MB (photo) / 2 GB (file)	1-5 MB	Send as "file" to avoid any compression

The Compression Sweet Spot

The ideal upload is an image that's already compressed enough that the platform's re-compression has minimal impact, but not so compressed that you've already degraded the quality yourself. For most platforms, that sweet spot looks like this:

Photos

Export as JPG at 85-92% quality. This removes invisible data without visible artifacts. The platform will compress it again, but starting at 85%+ means there's less to lose.

Graphics & Logos

Export as PNG-24 for sharp edges and text. If the PNG is under 1 MB, some platforms (Facebook, Twitter/X) will keep it lossless. Larger PNGs get converted to JPG server-side.

Mixed Content

Photos with text overlays or screenshots with both graphics and photos - export as JPG at 90-95%. The higher quality preserves text readability through re-compression.

Step-by-Step Compression Workflow

Follow these steps to get consistently sharp uploads across any platform. The goal is to give the platform an optimized file that's already close to its internal target - so it barely needs to touch it.

Start with the right dimensions

Check the cheat sheet or the platform-specific guide for exact pixel dimensions. Uploading an image that's larger than the platform displays means the platform has to downscale AND compress - two quality-losing operations. Match the recommended dimensions exactly, or go slightly over (1.5x at most).

Choose the right format

Photographs go to JPG. Graphics, logos, screenshots, and anything with text or sharp edges go to PNG. Not sure? Read the format comparison guide for detailed recommendations per platform.

Export at high quality

For JPG, export at 85-92% quality. Going below 80% introduces visible artifacts that get amplified by re-compression. Going above 95% adds file size without visible benefit - and bigger files trigger more aggressive platform compression.

Strip metadata

EXIF data (camera model, GPS coordinates, color profiles) can add 50-200 KB to every photo. Stripping it reduces file size without touching a single pixel. Most compression tools do this automatically. It also removes potentially sensitive location data from your uploads.

Run through a compression tool

Use a dedicated image compression tool for the final pass. These tools use smarter algorithms than "Save As" in Photoshop - they analyze each image individually and find the optimal compression that removes the most data with the least visible impact.

Free Image Compression Tools

You don't need Photoshop to compress images well. These free tools handle compression better than most paid software because they're purpose-built for it.

Browser-Based (No Install)

Squoosh (squoosh.app) - Built by Google. Lets you compare before/after side-by-side with a slider. Supports JPG, PNG, WebP, and AVIF. Works entirely in the browser - your images never leave your device.
TinyPNG (tinypng.com) - Drop up to 20 images at once, up to 5 MB each. Compresses PNG and JPG with minimal quality loss. Simple and fast.
Compressor.io (compressor.io) - Supports JPG, PNG, SVG, GIF, and WebP. Shows file size reduction percentage. Good for quick one-off compressions.

Desktop Applications

ImageOptim (Mac) - Drag and drop images to compress them. Strips metadata automatically. Replaces originals, so keep backups. Free and open source.
Caesium (Windows/Mac/Linux) - Batch compression with quality slider. Preview output before saving. Handles JPG, PNG, and WebP.
GIMP (Windows/Mac/Linux) - Full image editor with export quality controls. Use File > Export As to set JPG quality precisely. Free and open source.

Command Line (For Batch Processing)

If you regularly process dozens of images at once, command-line tools are the fastest option:

# JPG compression with mozjpeg

cjpeg -quality 88 input.jpg > output.jpg

# PNG compression with pngquant

pngquant --quality=65-80 input.png

# Batch compress all JPGs in a folder

for f in *.jpg; do cjpeg -quality 88 "$f" > "compressed/$f"; done

Platform-Specific Compression Tips

Each platform handles uploaded images differently. Here's what to know about the big ones.

Facebook & Instagram (Meta)

Meta converts almost everything to JPG after upload, even PNGs. The exception: PNGs under approximately 1 MB may be kept as-is. For photos, upload JPG at 85-90% quality at the recommended dimensions. For graphics with text, keep your PNG under 1 MB if possible.

Instagram is particularly aggressive with compression on images over 1080px wide. Stick to 1080px for feed posts and the re-compression is gentler. See the Instagram size guide for exact dimensions.

Twitter/X

Twitter has an interesting quirk: PNGs under about 900 KB stay lossless. So if you're posting a screenshot, infographic, or graphic with sharp text, export as PNG and keep it under that threshold. Photos should still be JPG at the recommended 1600 x 900 dimensions.

LinkedIn's compression is among the most aggressive. Feed images frequently come out looking noticeably softer than the original. Counter this by uploading at slightly higher resolution (2x the display size) and at JPG 90%+ quality. The extra pixels give the compression more to work with. Check the LinkedIn image guide for current specs.

Pinterest is friendlier to image quality than most platforms. Pins retain more detail because the platform's entire value proposition depends on visual quality. Upload at the recommended 1000 x 1500 dimensions and JPG at 85%+ quality. Don't over-compress - Pinterest won't compress it much further.

Common Compression Mistakes

Uploading massive files "for quality"

A 20 MB photo doesn't look better on Instagram than a 2 MB one at the same dimensions. The platform compresses both to roughly the same output - but the 20 MB file triggers more aggressive compression because there's more data to strip away. Bigger files don't mean better quality after platform processing.

Saving JPGs multiple times

Every time you open a JPG, edit it, and save it again as JPG, you lose quality. This is generational loss - the same thing that happened with analog tape copies. Always keep your original (PSD, TIFF, RAW, or PNG) and only export to JPG as the final step before uploading.

Using screenshots instead of exports

Taking a screenshot of your design and uploading that is tempting when you're in a rush. But screenshots are captured at screen resolution (usually 72 or 144 DPI), may include color profile mismatches, and are sized to your monitor rather than the platform's recommended dimensions. Always export from your design tool at the exact target size.

Compressing below 70% quality

Dropping JPG quality below 70% creates visible blocking artifacts around edges and in gradient areas. After the platform compresses it again, those artifacts become even more pronounced. The file size savings between 70% and 50% quality are small compared to the quality loss. Stay above 80% for anything that matters.

Quick Reference: Optimal Upload Settings

Image Type	Format	Quality	Target File Size
Photos (feed posts)	JPG	85-92%	500 KB - 2 MB
Cover photos / banners	JPG	88-95%	500 KB - 3 MB
Logos / icons	PNG-24	Lossless	Under 500 KB
Screenshots / infographics	PNG	Lossless	Under 1 MB (ideal)
Photos with text overlay	JPG	90-95%	1-3 MB
Profile pictures	PNG	Lossless	Under 500 KB

Frequently Asked Questions

Does uploading a PNG always give better quality than JPG?

Not necessarily. PNGs are lossless, so they start with perfect quality. But if the PNG is large (over 1 MB), most platforms will convert it to JPG server-side anyway - and you lose control over how aggressive that conversion is. A well-compressed JPG at 90% quality often looks better after platform processing than a large PNG that got aggressively converted. The exception is small PNGs (under 1 MB on Facebook, under 900 KB on Twitter/X) which some platforms keep as-is.

Why does my image look fine on desktop but blurry on mobile?

Modern phones have high-density displays (2x or 3x pixel density). An image that looks sharp at 100% zoom on a desktop monitor looks soft on a phone because the phone is trying to display it at 2-3x the pixels. The fix is simple: export at the platform's recommended dimensions, which already account for retina displays. Don't export at half-size thinking the platform will scale it up - it won't look good.

Should I use WebP for social media?

WebP offers better compression than JPG at the same quality level, but support varies across social platforms. Facebook and Twitter/X accept WebP uploads, but many other platforms either don't support it or convert it to JPG internally. For maximum compatibility, stick with JPG for photos and PNG for graphics. WebP is better suited for websites where you control the display environment. Read the format guide for platform-by-platform format support.

Can I avoid platform compression entirely?

On most platforms, no - compression happens automatically. But there are a few workarounds. On Twitter/X, PNGs under ~900 KB stay lossless. On Telegram, sending an image as a "file" instead of a "photo" preserves the original quality. On Discord, images under the file size limit aren't noticeably re-compressed. For everything else, the best strategy is pre-compressing your image to a size close to the platform's internal target so the re-compression pass has minimal impact.