Skip to main content

A bigger export cannot fix a tiny detail

Twitter image size: keep the important detail readable

Your screenshot looks sharp on your monitor, but the useful part disappears on a phone. Choose the crop around what readers need to see before increasing the pixel count.

By ImNotAVirus Updated November 18, 2026
On this page

Choose dimensions around the detail, not the whole screen

You export a large screenshot, attach it to a Twitter post, and discover that the label you wanted people to read is tiny. More pixels can preserve the file's detail without making that detail easier to notice in the feed.

For a single attached photo, X's photo posting guide says aspect ratios from 2:1 to 3:4 display in full. Its file requirements allow photos up to 5 MB and accept JPEG, PNG, and GIF. That is guidance for photos, not a universal canvas size for every Twitter surface.

These are example export sizes you can start with, not required X dimensions:

ShapeExample dimensionsWhen to try it
Landscape, 16:91200 × 675 pixelsA wide comparison or a focused horizontal screenshot.
Square, 1:11200 × 1200 pixelsA compact chart or a subject that needs similar space in both directions.
Portrait, 3:41200 × 1600 pixelsA vertical subject that still reads without a long stack of tiny text.

All three examples sit within that documented single-photo range. None guarantees that a reader will understand the image or that the post will get more reach. Keep the original file, then make an export that gives the important detail enough room.

This guide concerns a photo attached to a post. A profile banner has a different job. An image in a link preview comes from the linked page's metadata; resizing a separate attachment does not fix that card.

Crop the distraction without cutting away the explanation

A full desktop capture often spends most of its area on navigation, empty space, and controls the reader does not need. Crop around the change you are explaining, while leaving enough context to interpret it.

For a chart, keep the metric, period, and relevant axes. If removing an axis makes a small change look dramatic, the crop has changed the claim. For a before-and-after comparison, use comparable framing so the reader can see the difference rather than guess which state is which.

Try reading the export at the size it will occupy on your phone. If the post depends on a number you cannot read there, enlarge that part of the composition or move the number into the post text. Do not rely on someone opening the photo to discover why it matters.

Resizing a low-resolution capture cannot recover information that was never recorded. Return to the source and capture the useful region clearly. Remove private names, unrelated tabs, and confidential details before uploading the file.

If you have not decided what the image adds, use the image-versus-text guide first. A perfectly sized attachment is still extra work when the sentence explains the idea on its own.

Check the file in the composer you will actually use

X documents cropping controls in its mobile apps. An export from your design tool and a crop applied during upload are different versions of the image, so inspect the final attachment.

  1. Export the chosen crop as a still JPEG or PNG and check its dimensions and file size.
  2. Attach that file using the app or publishing tool you intend to use.
  3. Check the preview, image order, and any crop applied there. For multiple images, inspect the whole composition rather than assuming the single-photo rule describes it.
  4. Review the post text and each image description together before approving publication.

If the file is rejected, record the tool, format, byte size, and exact error before changing the export. A smaller pixel width is not the same thing as a smaller file: compression and image content also affect the bytes.

If compression blurs the labels, simplify the composition and export again from the source. Put a long explanation in the post text instead of shrinking more words into the image.

Describe what the reader needs from the image

X's image-description guidance recommends including important information and writing out or summarizing text in the image. For complex visuals, describe the relevant findings and provide the supporting source in the post when needed.

An image description serves readers who cannot use the picture as you do. It does not make tiny labels easier for a sighted reader to read. Fix both the composition and the description; our Twitter alt text guide has examples for screenshots and charts.

Check that the description still matches the final crop. A description of the original full screen may refer to a panel you removed from the exported attachment.

Save the export decision with the draft

Keep a short preparation note so you do not have to reconstruct the choice when you return to the post:

Detail the reader must see:
Original source file:
Export dimensions and aspect ratio:
File format and byte size:
Context that must stay visible:
Phone-size reading check:
Final image order and description:

PilotMyX supports drafts with ordered images and alt text. Attach the approved export, review its wording and image order, then approve the publication time. The export and cropping decisions still need your review; storing a draft does not establish how every X client will display it.

After publication, keep legibility separate from performance. PilotMyX can show collected post text and available metrics such as impressions or profile visits, with capture times. Those counters cannot tell you whether someone read a small label in the image.

For a comparison with earlier posts, keep the topic and measurement age similar, and record changes to the wording or timing. A stronger result can suggest another test; it cannot establish that the export dimensions caused it.

Use your own account

Turn the next guess into a decision you can test.

Prepare my next image post
PilotMyX

Your account. Your data.

Here’s what PilotMyX needs, and what it doesn’t.

Only what makes the product work

Your posts, replies and stats, plus your profile to identify your account.

Not for sale. Not for ads.

We don’t sell your personal data. Your connected X data is used to run PilotMyX, not for advertising.

Your connection is protected

Access tokens are encrypted. We never see your password or read your DMs. You can revoke access anytime in X.

X asks for publishing access so you can schedule posts. We only publish when you, or an agent you authorize, ask us to.

Any question? You can reach me directly here: