Free · Fast · Privacy-first

Compress Image for Twitter / X

Twitter, now branded as X, converts every uploaded image to JPEG and applies its own compression as part of media processing, which can noticeably degrade photo quality especially when the source file is large.

⚡

Pre-empt Twitter's JPEG conversion

🔒

Stay under Twitter's 5MB upload limit

✨

Recommended: 1200x675px for tweet images

⚡

No watermark on downloads

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

FreeNo signupWhite-label

Add this Image Compressor to your website

Drop the Image Compressor into any page — blog post, product docs, intranet, school portal — with a single line of HTML. Your visitors get the full tool, processed entirely in their browser. No backend, no uploads, no signup.

Files stay 100% in the visitor's browser
Responsive — adapts to any container width
Free forever, no API key needed

Embed code

<iframe
  src="https://www.fixtools.io/image-tools/image-compressor?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Image Compressor by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

<iframe
  src="https://www.fixtools.io/image-tools/image-compressor?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Image Compressor by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.

Twitter's 5MB limit, platform auto-JPEG conversion, and the pre-compression strategy

Twitter converts every uploaded image to JPEG as part of its media processing pipeline regardless of the format you upload. A PNG file uploaded to Twitter is converted to JPEG during processing. A HEIC file is converted to JPEG. Even an existing JPEG is re-encoded through Twitter's own JPEG compressor, which applies quality settings calibrated for Twitter's bandwidth and storage costs rather than for image quality preservation. The result of Twitter's conversion is a JPEG at approximately 85 to 90 percent quality for images well under 1 megabyte, and more aggressive compression at 70 to 80 percent quality equivalent for larger files. Twitter's compression is more aggressive for images with small dimensions combined with complex content, and less aggressive for large-dimension images with high-quality source material that match Twitter's display targets.

The 5 megabyte upload limit for photos on Twitter as of 2024, with PNGs up to 5 megabytes and GIFs up to 15 megabytes, creates a practical ceiling, but most users hit quality problems well below this limit. A 4 megabyte full-resolution photo receives more aggressive Twitter compression than an 800 kilobyte pre-compressed photo because Twitter's pipeline targets a specific output file size range for feed display. By pre-compressing to 85 percent quality at 1200x675 pixels, producing a file of approximately 250 to 400 kilobytes, you give Twitter a source that is already near its target output range. Twitter's compression pass on a 300 kilobyte source is much lighter than its pass on a 4 megabyte source, resulting in a noticeably sharper final displayed image.

The 1200x675 pixel dimension at 16 to 9 ratio is the optimal single-image tweet dimension because it matches the feed display size exactly. Twitter displays single tweet images at 1200 pixels wide on desktop with responsive scaling on mobile. Uploading at exactly 1200x675 pixels eliminates any resize step from Twitter's processing pipeline. Images at other aspect ratios are cropped in the feed preview, with Twitter showing a 16 to 9 crop in the timeline and revealing the full image only when clicked. Square images at 1 to 1 ratio and portrait images at 4 to 5 ratio are also well-supported but show smaller previews in the desktop timeline. For maximum visual impact in the feed where most users only see the preview, 1200x675 pixels at 16 to 9 is the recommended format.

A practical consideration that often catches users off guard is that Twitter's compression is applied to the displayed image, not to the original you uploaded. Even if you upload a perfect file, what your followers see is Twitter's compressed version. The only way to influence that outcome is to give Twitter a source that produces the best possible compression result, which means correct dimensions, correct format, and moderate file size that lands within Twitter's lightest-compression band. Pre-compression is not about preserving your original file inside Twitter; it is about steering Twitter's pipeline toward the best possible output.

Twitter / X image upload specifications Twitter media best practices for developers JPEG compression artifacts (Wikipedia)

How It Works

Step-by-step guide to compress image for twitter / x:

1
Resize to Twitter dimensions
Use the Image Resizer to set your image to 1200x675 pixels, which is the 16 to 9 ratio used for single tweet images in the desktop feed. Matching these dimensions exactly eliminates Twitter's resize step from the pipeline and preserves more detail in the final displayed image.
2
Convert to JPG if needed
Twitter converts all uploaded images to JPEG during processing. Use the Format Converter to convert PNG to JPG yourself first at 85 to 88 percent quality, avoiding the double-conversion artifacts that occur when Twitter does the PNG-to-JPEG conversion in its own pipeline with aggressive settings.
3
Compress to 85% quality
Upload the JPG to the Image Compressor, set quality to 85 percent, and download. This produces a clean source for Twitter's processing that is small enough to receive Twitter's lightest compression pass rather than its most aggressive one.
4
Upload to Twitter/X
Attach the compressed image to your tweet through the desktop website at twitter.com or x.com for best results. It should display sharply in the feed without further visible quality loss compared to your pre-compressed source.

Real-world examples

Common situations where this approach makes a real difference:

Journalist

A news journalist tweets breaking news photos directly from the field where speed matters as much as quality. Original phone photos are 7 to 9 megabytes. After compressing to 85 percent quality at 1200x675 pixels, producing 280 to 350 kilobyte files in Chrome on an Android phone, images attach to tweets without triggering Twitter's heaviest recompression band. Followers report that detail and text in the photos are readable, unlike the journalist's previous direct-upload photos which became too blurry to read on phones.

Brand social media manager

A consumer brand's social media team posts product campaign images daily on Twitter. Agency-supplied JPEGs are 3 to 5 megabytes at 3000x1688 pixels. After establishing a workflow of resizing to 1200x675 pixels and compressing to 85 percent in FixTools before scheduling in Buffer, every tweet image displays with consistent sharpness across the campaign. The brand's engagement rate on image tweets improves 18 percent compared to their previous direct-upload workflow that left images visibly degraded in the feed.

Sports photographer

A sports photographer tweets action shots from events while still in the venue. Original 24 megapixel JPEG files are 8 to 12 megabytes. After compressing to 85 percent quality at 1200x675 pixels, producing 290 to 420 kilobyte files, images attach quickly from the phone and display with sharp athlete detail in the feed. The pre-compression step takes 40 seconds per image in Safari, which fits within the photographer's two-minute post-deadline workflow between plays.

Infographic creator

A data journalist creates statistical infographics as PNG files at 1200x675 pixels weighing 2 to 4 megabytes each. After converting PNG to JPEG at 88 percent quality, which preserves text legibility, before uploading to Twitter, the infographics display with readable text in the feed. Converting PNG to JPEG before Twitter's own PNG-to-JPEG conversion eliminates the double-conversion artifact that previously made small-font text in the infographic blurry and undermined the entire point of sharing the chart.

Pro tips

Get better results with these expert suggestions:

Convert PNG to JPEG before uploading to avoid double-conversion

Twitter converts all PNG uploads to JPEG during processing. A PNG-to-JPEG conversion at Twitter's quality settings can introduce significant artifacts, especially on images with smooth gradients and fine text. Converting PNG to JPEG yourself at 85 to 88 percent quality using the Format Converter means Twitter receives a JPEG source and does not perform a PNG-to-JPEG conversion itself. Only Twitter's standard JPEG compression pass applies, not the format-change conversion that compounds artifacts.

Upload pre-compressed images under 1MB for the lightest Twitter processing

Twitter's compression is progressively more aggressive for larger source files. An image under 1 megabyte receives a lighter compression pass than a 4 megabyte image. By pre-compressing to 85 percent quality at 1200x675 pixels, which typically produces 250 to 400 kilobyte files, you give Twitter a source that is already near its target output range, minimizing the quality degradation from Twitter's compression step and producing visibly sharper results.

Use 1200x675px for maximum desktop feed presence

Twitter crops images in the timeline to a 16 to 9 preview on desktop. An image at exactly 1200x675 pixels fills this preview completely without cropping and requires no resize from Twitter's pipeline. Images at other dimensions show a cropped preview that users must click to see in full, which reduces the chance they engage with the full composition. For brand content and news images where the full frame matters, 1200x675 pixels ensures the full image is visible at a glance.

For PNG graphics with text, use JPEG quality 88 to 90 percent to preserve text legibility

Infographics, charts, and graphics with overlaid text are sensitive to JPEG compression at the text edges. Using quality 88 to 90 percent rather than the standard 85 percent preserves text legibility through the two-step compression process of your pre-compression plus Twitter's compression. The slightly larger file size, typically 15 to 25 percent more than at 85 percent, is well within Twitter's 5 megabyte limit at 1200x675 pixels and worth the readability gain.

FAQ

Frequently asked questions

Twitter accepts images up to 5 megabytes for photos in JPEG and PNG. GIF files can be up to 15 megabytes. Video files follow separate limits with their own size and duration constraints. The 5 megabyte limit for photos is rarely the binding constraint because most quality issues occur because Twitter's compression pipeline is more aggressive for larger source files. Pre-compressing to under 1 megabyte at 1200x675 pixels is more effective than simply staying under 5 megabytes.

Yes, every time. Twitter converts all uploaded images to JPEG and applies its own compression to every uploaded image during processing. The compression is more aggressive for larger source files. Uploading a pre-compressed 300 kilobyte JPEG results in lighter additional compression than uploading a raw 5 megabyte JPEG. Pre-compressing at 85 percent quality at the correct display dimensions produces the sharpest final result in the Twitter feed because it lands in Twitter's lightest-compression band.

Use 1200x675 pixels at 16 to 9 ratio for single images in tweets because this matches Twitter's feed display size exactly and prevents any cropping in the timeline preview. For square images use 1200x1200 pixels. For portrait format use 1200x1500 pixels at 4 to 5 ratio. Twitter supports multiple images in a tweet up to four total, which display in a 2 by 2 grid at smaller individual sizes per image with their own per-tile aspect handling.

JPEG is strongly recommended for photographs and most content types. Twitter converts PNG to JPEG during its processing pipeline, which introduces JPEG artifacts into an image that was previously lossless. Starting with JPEG means Twitter's pipeline only applies compression, not format conversion plus compression. For graphics with sharp text where PNG preserves edges better, the tradeoff may favor PNG, but use quality 88 to 90 percent for your pre-compression to maintain text legibility through two compression passes.

Pixelation in Twitter images usually means the source image was too large, causing heavy resize plus compression in Twitter's pipeline, or the source was already a low-quality JPEG that suffered double compression artifacts. The fix is to resize to 1200x675 pixels before uploading and use a JPEG source at 85 to 88 percent quality. At these settings, Twitter's pipeline applies only light additional compression, producing a clean final image that does not show pixelation in the feed.

Yes. Open fixtools.io in Safari on iPhone or Chrome on Android, upload the photo you want to tweet, resize to 1200x675 pixels using the Image Resizer, compress to 85 percent quality, and save to your photo library. Then attach the saved compressed image to your tweet in the Twitter app. The extra two to three minutes of preparation per tweet produces noticeably sharper images than uploading originals directly and is worth it for content you care about.

No. Twitter applies a format-conversion step to PNG files, converting PNG to JPEG, in addition to its standard compression pass. This double processing degrades PNG files more than JPEG files of equivalent visual quality. For the same source dimensions and visual quality, a pre-compressed JPEG survives Twitter's pipeline better than a PNG. Convert PNGs to JPEG before uploading to Twitter for all image types except those where PNG's transparency is essential, which Twitter does not preserve anyway.

Use JPEG quality 85 percent for photographs at 1200x675 pixels. This produces files of 250 to 400 kilobytes for most photographic content, well under Twitter's 5 megabyte limit and light enough that Twitter's compression pass is minimal. For graphics with text, such as infographics and quote cards, use 88 to 90 percent to preserve text legibility through the two-pass compression process. Avoid quality below 80 percent for Twitter-bound images because artifacts from your compression compound with Twitter's pass.

Twitter allows up to four images per tweet, which display in a tiled grid layout that adjusts based on how many images you attach. For two images they tile side by side; for three or four they tile in a 2 by 2 grid with the layout adjusted for the count. Each image still goes through Twitter's compression individually, so pre-compressing each one at 85 percent quality and the appropriate dimensions produces the best result regardless of how many you attach.

Twitter strips most EXIF metadata from uploaded images during processing, including GPS location, camera model, and shooting data. This happens regardless of whether you pre-compress because Twitter's pipeline does the stripping as part of its standard processing. FixTools also strips EXIF during compression as a side effect of Canvas re-encoding, so by the time your file reaches Twitter, EXIF is already removed and Twitter's strip step has nothing additional to do. Twitter (X) automatically re-compresses uploaded images, so always start with the highest quality you can afford bandwidth-wise.

Twitter accepts images up to 5MB for JPG and PNG, and 15MB for animated GIFs. However, Twitter automatically re-compresses uploaded images, so the visible quality on your timeline may be lower than the original you uploaded. To maintain quality after Twitter's re-compression, upload images at slightly higher resolution than the display size (e.g., 1600x900 for landscape posts displayed at 1200x675) so that even after compression the displayed result remains sharp. Twitter's image processing favors JPG for photographs and PNG for graphics with text or sharp edges.