How to save a photo from X at full resolution

#Quick answer

To save a photo from X, press and hold the image in the X app and choose the save option, or right-click it on x.com and pick "Save image as". That gets you a resized copy, not the original. For the biggest version X holds, open the image in its own tab so the address bar shows a pbs.twimg.com URL, then add ?format=jpg&name=orig to the end and save that. On a file checked on 6 October 2026, the default copy came back at 1200 x 675 and the orig copy at 1920 x 1080.

Last updated: October 2026

#TL;DR

Every page ranking for this query is a downloader tool, which is why they all stop at "paste the link, press the button". None of them tell you the part that actually matters: there are at least four different copies of every photo sitting on X's media servers, and the one your browser saves by default is the small one.

X's own help center quietly confirms the gap. There is a detailed page on posting photos or GIFs covering iOS, Android, web, Live Photos and GIF search. There is no page on saving one. The only download X documents at all is for video, and it is gated to Premium.

So this guide covers the native route per platform, the parameter that gets you the original, why the file has no metadata in it, what a missing save button really means, and where the copyright line actually sits.

#The native save routes

That save item has moved around between app versions, which is why half the complaints about it being "removed" are really about it being relocated. If the three dot menu looks bare, go back to the image and hold your finger on it instead. That gesture has survived every redesign.

Two things do not happen when you save. The author is not notified, and nothing appears on your profile. Saving is invisible, unlike a bookmark, which at least adds to the public bookmark count on the post.

One loss worth knowing about: the file does not carry the alt text. If the photo was a chart or a screenshot with a written description attached, that description lives on the post, not in the JPEG, and it is gone the moment you save. The same asymmetry is why alt text on X cannot be edited after posting.

#The resolution problem, measured

Here is the part no downloader page explains. X stores several renditions of each upload and serves whichever one fits the view. Request the same media file with a different name value and you get a different file back.

These are the actual responses from one post's media file, checked on 6 October 2026:

Double the pixels and double the file size, from editing one word in a URL. The practical steps:

1. Open the photo full screen on x.com.
2. Right-click and choose "Open image in new tab", or "Copy image address" and paste it into the address bar. The URL starts with pbs.twimg.com/media/.
3. Replace everything after the file ID with ?format=jpg&name=orig.
4. Save the image that loads.

On this file large and orig returned the same bytes, which happens whenever the upload was no bigger than X's large rendition. On a high-megapixel upload they diverge, and orig is the one to ask for. The format parameter is not a converter: it only serves a format the stored file supports, which is why format=png returned a 404 on a JPEG upload rather than a PNG.

Mobile browsers make step 2 awkward because there is no right-click. Switching to the desktop site, or doing this bit on a laptop, is less fiddly than installing anything. If you want the full picture of how X resizes and crops what you upload in the first place, that is covered in X image sizes.

#What orig does not mean

orig is the largest copy X kept. It is not the file that left the poster's camera.

X re-encodes uploads on the way in. The 316 KB file above is progressive JPEG, and it contains no EXIF block: no GPS coordinates, no camera body, no capture timestamp. That is consistent with what OSINT researchers document about X's media pipeline, which is that served images are stripped of EXIF and reduced in quality relative to the original.

For most people that is good news. It means posting a holiday photo does not hand strangers the coordinates of your house. If you were hoping to recover a metadata trail from a saved image, though, stop looking: it was removed at upload, not at download.

#When there is no save option

Work through these in order, because the answer is almost never "X took the feature away".

It is a GIF, not a photo. GIFs on X behave as short looping video files, so the photo gesture does not apply to them. Posting one has its own quirks, covered in how to post a GIF on X.

It is a video. This one is a real restriction rather than a UI hunt. X's video help page says Premium subscribers can download videos from certain posts for offline viewing or remixing, through the three dot icon then Download video. On a free account that item does not appear, and the full set of conditions is in how to download a video from X.

The media is behind a warning. Content flagged as sensitive is hidden until you reveal it, and you cannot save what has not been rendered. Your account-level setting for that is in sensitive content on X.

The account is protected. If you cannot see the post, there is nothing to save. Protected posts are also the case where saving and resharing is most clearly a breach of the poster's expectations, whatever the technology allows.

#Your own photos: use the archive

If the goal is every photo you have ever posted, saving them one at a time is the wrong tool. Request your archive instead. X's archive route is the documented way to get your own data, the download includes your media, and the whole process is covered in how to download your X archive. It is not instant: X builds the file and emails you when it is ready.

#The copyright line

A save is a copy, and the ease of the gesture has no bearing on the rights.

X runs copyright enforcement through DMCA notices, and its copyright policy names the unauthorized use of an image uploaded through media hosting as exactly the kind of complaint it acts on. The same policy includes the sentence most reposters skip: not all unauthorized uses of copyrighted materials are infringements, because fair use protections may apply.

In practice the risk sits with what you do next, not with the save. Keeping a reference image in a folder is not what generates complaints. Reuploading someone's photograph as your own post, cropped to hide the watermark, is. If you are on the receiving end of that, the counter-notice path and the filing form are both in X copyright claim.

A note on the downloader sites that own this SERP: they work, and the cost is that you hand a stranger's server the URL of every post you were looking at, usually in exchange for watching an ad. The CDN parameter above does the same job with no third party in the middle.

#If you are saving photos to repost them

Plenty of people land here because they run a visual account and are building a library of other people's images to post. That is a fragile strategy on two counts: it is the exact behaviour the copyright policy above is written for, and reposted media has no reason to bring anyone back to your account.

Accounts that compound are the ones that show up consistently with something of their own. That is slow by hand, which is where our tool comes in: X-Autopilot drafts posts and replies in your voice and runs them through real Chrome on your own Mac, so the session cookie stays on your machine and the traffic leaves from your home IP rather than a shared cloud pool. That is a smaller detection surface than a cloud scheduler, not an absence of risk, and automating engagement through a browser sits outside what X's automation rules sanction. What the account does stays your responsibility.

The short version: hold the image, save it, and if the result looks soft, go get name=orig.