Twitter Photo Download: Get the Original Resolution

Contents
- Why the photo you see on screen feels different from the one you saved
- How to get the original by editing the photo URL yourself
- Why the photo you see on screen differs in size from the original file
- Image quality and file size by saving method
- Common places you get stuck
- Can I use the photos I saved however I want?
- How this differs from other saving methods
- The Bottom Line
- Frequently Asked Questions
If you've ever saved a photo from Twitter (X) and then zoomed in only to find it blurry and smeared, you're not alone. The problem isn't that you saved it the wrong way. It's that the photo you see on screen was never the original upload to begin with. You can get the original resolution by changing the photo's URL slightly, and you can see the difference for yourself using a photo posted by an official account. This post explains why the difference exists and how to check for the original, step by step.
Summary ① Photos you get from the timeline or the save button are not the original upload. They're reduced copies sized for on-screen display. ② Change the parameter at the end of the photo URL to orig to get the original resolution. Using a photo from NASA's official Artemis account, we confirmed the actual 5568×3712 original. ③ Tweets with a GIF or video attached, private accounts, and deleted posts can't be retrieved this way.
Why the photo you see on screen feels different from the one you saved
Viewing a photo in your Twitter timeline and tapping the save button, or right-clicking and choosing "Save image," is a familiar move for anyone. But when you open the saved file, it can feel somehow different from what you saw on screen.
Say an online seller saves a product photo from Twitter for reference and blows it up for a printed flyer or product page. The edges can look like jagged steps. It looked fine on screen, but the problem shows up the moment you enlarge it.
It's also common to save a photo from your favorite artist's or athlete's official account to use as a wallpaper, then see it stretch and look blurry when it fills your monitor. The file simply has fewer pixels than your monitor's resolution.
In both cases, you didn't save it wrong. Twitter displays a version that's compressed smaller than the upload, and the save button grabs that exact file that's on screen.
Taking a screenshot gives you the same result. You're capturing the pixels shown on screen, so if the on-screen image was scaled down, the screenshot is just as small. It's actually worse in one way: the result changes every time depending on your display scaling or browser window size.
The tricky part is that it's hard to tell the reduced copy from the original by eye. Unless you zoom in a lot or print it, they look about the same on a phone or laptop screen. So you notice the problem late, often when you're already trying to use the photo for something else.
On top of that, Twitter gives you several ways to "save" a photo. There's the save button in the app's share menu, right-click save in a browser, and tapping a photo to enlarge it and then saving again. Whichever route you take, you're downloading the image file that was already on screen. Switching routes won't get you the original.
The same problem comes up when you quote a tweet's photo and run it large in an article or blog post. On a phone screen, the display size is small, so the quality difference is hard to see. The moment you move it to a bigger display, like a PC monitor, projector, or printed page, the compression artifacts show up clearly.
The root cause of all this is that "I saved it" and "I got the original" don't mean the same thing. When you hit the save button, you assume you're downloading the file as it exists on the server. In reality, you're just getting the file that's already on screen, prepared for display.
Switching between the app and the browser won't change the outcome much. Every route ultimately downloads the file that was rendered on screen, so changing apps or browsers doesn't fix the blur.
Sometimes you save a photo to share in a community or group chat, then zoom in and find it smeared, so you have to ask again. You go back to Twitter thinking the original must be somewhere, but the photo shown there is still the same reduced file you saved the first time.
In the end, image quality isn't about how you saved it. It's about what you saved. Changing where the save button is or which app you use won't help. If the file on screen was already a reduced copy, the result will be a reduced copy too.
This problem also gets in the way when you're saving photos to print and keep for years, like a graduation album or a memory album. You don't notice at the time. Years later, when you go to order prints, you find the file is too small to enlarge.
It's also common for someone managing a company or organization account to save a photo from Twitter for promotional materials. When you're re-editing a photo for a banner or social media card, anything less than the original resolution drags down the quality of the final piece.
And if you repost a saved photo to another social network, that app may compress it again during upload. Stack another round of compression on top of an already reduced photo, and the quality loss becomes much more obvious than when you first saved it from Twitter.
As phone and tablet screens have gotten sharper, this difference has become easier to see. The denser the screen, the more the compressed edges and color blotches stand out. A blur that might have gone unnoticed a few years ago is obvious on today's devices.
For what it's worth, this isn't limited to photos. Videos often start with a stream optimized for on-screen display too. But video is outside the scope of this post, so I'll stick to photos here.
You might also blow up a tweet photo for a video conference or presentation slide, only to see the pixels stand out the moment it hits the screen. It's an awkward experience, and there's no undoing it mid-presentation.
Some people only regret not saving the original after an account disappears or a tweet is deleted. Once a post is gone, this method can't bring it back. The more important the photo, the more it pays to check that you're saving the original from the start.
Original resolution also helps when you're trying to trace a photo's source or run a reverse image search. Search engines tend to return more accurate results with a sharp original than with a small, blurry image, so a reduced copy alone may not find what you're looking for.
How to get the original by editing the photo URL yourself
There's a way to get the original by editing the actual photo address Twitter (X) uses to show images on screen. You can do it in a browser, no tool required.
Start by right-clicking the photo and choosing "Copy image address." On a mobile browser, long-press the photo to find the same menu. The address you copy this way — called media_url_https — is the real location where the photo is stored.
Menu names differ slightly from browser to browser. Even if yours says something else, you can get the same result by opening the photo on its own in a new tab and reading the address bar from there. What matters is not the menu name, but getting an address that holds nothing except the photo file.
Here's one thing that's easy to mix up. A tweet's share link and the photo address you just copied are not the same. Paste the tweet link into your address bar and you get the whole Twitter page, not the photo file. To open the photo file, you have to use the address you copied separately from the image itself — the one that starts with the image-only domain. If you confuse the two and tack parameters onto the tweet link, you won't get what you want.
The "enlarge" view works the same way. Clicking a photo inside Twitter makes it fill the screen, but the browser is just stretching the same compressed copy to fit your display. The actual file resolution doesn't go up. Big on screen doesn't mean original — this is another place where that shows.
Paste the copied address into a new tab and you'll see a file extension at the end (.jpg, .png, and so on). Delete that extension and put a question mark in its place, followed by the value format=jpg&name=orig. After format, use jpg or png to match the original file type.
Load the edited address again and a much larger photo opens in your browser. Right-click and save from there, and that's the uploaded original. If the value after name is something other than orig, or missing entirely, you're downloading the compressed copy Twitter made for display.
To sum up, the order is:
- Right-click the photo → Copy image address
- Paste it into a new tab's address bar
- Delete the extension at the end and add format=jpg&name=orig after a question mark
- Press Enter, then right-click the photo that opens and save it
There are traps in this method too. If you miss the exact spot where the extension ends, or type a different symbol instead of the question mark, the browser can't open the photo at all and just shows a broken image icon. When that happens, the fastest fix is to copy the address again from scratch and recheck where the extension ends.
After saving, get in the habit of opening the file and checking its width and height in pixels. A true original comes out in the thousands of pixels wide, like a photo from a recent smartphone camera. If the file you saved is still in the hundreds of pixels, a parameter got dropped or attached wrong somewhere.
If you want to verify before saving, you can right-click the open photo and choose "Inspect." The developer tools panel sometimes shows the actual file size. Keep in mind that the menu name and the way it's displayed vary by browser, so it can feel unfamiliar on your first try.
And because this means hand-editing a string for every single photo, mistakes pile up when you're rushing through a batch — extensions left in place, parameters misspelled. You can't tell a compressed copy from an original just by looking, so you only notice the error later, at the moment you need the photo for something else.
One photo and this isn't hard. The problem is a tweet with several photos attached. If a tweet has four photos, you copy the address, strip the extension, add the parameter, and save — four times over. If it's a thread, that work multiplies by the number of tweets.
On mobile it's more of a chore. You go back and forth pasting into the address bar, deleting, and pasting again, and the small screen makes it hard to remove the extension cleanly. Rather than repeating that for every photo, a tool that takes the pasted address and handles the original download and ZIP export in one go is much faster.
Free · No login needed · Select multiple photos and save them all as a ZIP in original resolution at once

Why the photo you see on screen differs in size from the original file
The screen above shows this tool's readout for a tweet from NASA's official Artemis account, which posted photos from the Artemis II mission. All four photos came back at the same resolution: 5568×3712. That's far bigger than the shrunken copy you saw in your timeline, scaled to fit your screen.
The way this tool finds photos is to use the syndication (embed) API that Twitter publishes, exactly as it is. The syndication API is a channel Twitter built so other websites can embed and display tweets. When that API hands back tweet data, each photo arrives with its stored address in a field called media_url_https.
The syndication API is the channel Twitter opened up so news sites and blogs can embed public tweets without a Twitter login. If you've ever seen a tweet sitting inside an article as a card, this API is what's running behind it. This tool just puts the same channel to work pulling out photo addresses.
There's nothing unusual about why display images come down smaller than the original. Sending the full original every time makes photos slower to load and burns more data — especially on a timeline where several photos scroll past at once. So a photo that will show up small gets delivered as a scaled-down copy first, and the original only comes down when you explicitly ask for it.
The key point is that the media_url_https address itself is not the display-size copy. If you open that address with no parameters attached, Twitter's server sends a compressed version by default. You have to strip the extension off the end and put format=jpg&name=orig in its place — then the same address gets the original resolution back from the server. This tool adds that parameter for every photo automatically, so the original comes out of the address directly.
You never have to deal with photo addresses yourself. The only thing you put into this tool is the tweet's share link. It passes that link to the syndication API, gets back the photo list and the media_url_https values, and handles the parameter step inside the tool. The whole manual procedure described above runs behind the screen on its own.
Even if you understand this structure, it's easy to miss if you never actually compare the two sizes side by side. We treat viewing a photo on screen and downloading the file as the same act, so many people never notice they've been downloading the reduced copy the whole time. Once you put the two sizes next to each other — as with the NASA Artemis account — the difference is obvious.
There's a reason we checked with the NASA Artemis account specifically. Mission photos from official agency accounts are usually shot as high-resolution originals and are unlikely to be deleted or made private, which makes them good for repeated verification. Opening each of the four photos attached to the tweet one at a time and getting 5568×3712 every time means the account uploaded the originals as-is, and this tool found every one of them.
We opened all four individually because problems can hit each photo in a tweet separately. If one photo in a multi-photo tweet was re-uploaded at a different time, or went up with different compression settings, the results can differ per photo. In this check all four came back at 5568×3712, which also confirms the account uploaded all of them the same way.
This parameter approach works the same whether the photo is jpg or png. The tool reads the address and attaches the parameter that matches the original file format, so you don't have to think about file formats at all.
The value name orig is short for "original." As the parameter name suggests, it was designed from the start to point at the original. The photo you get when that value is missing, by contrast, is a separate file optimized for display.
The same structure is why one link to a multi-photo tweet returns the entire photo list at once. When you ask the syndication API about a single tweet, all the media_url_https values for its photos come back together. The list is built in one pass with no separate request per photo, so other than ticking checkboxes, there's no waiting.
To grab several at once, tick the photos you want in the list and press Save ZIP. The ZIP file is assembled right there in your browser. It isn't a case of uploading the photos to a server, compressing them, and sending them back — the browser already has each photo at original resolution and bundles them locally into one archive.
That assembly uses only features built into the browser, with nothing to install. Compared with right-clicking and saving photos one by one, you make fewer clicks, and the photos you picked never go up to a tool server and back down — they're packed into a file inside your browser.
The ZIP is built in store (no compression) mode. JPG and PNG are already compressed formats, so running zip compression on top barely shrinks the file. It just costs extra time. Store mode skips compression and only bundles the files as they are, so the ZIP appears right away no matter how many photos you select. And because the whole process finishes inside your browser, the photos you picked aren't left in any server storage.
If you paste a tweet with a GIF or video instead of photos, the tool points you to the "X (Twitter) Video Downloader." Photos and videos are stored in completely different forms in the tweet data, so assembling an original photo address and rebuilding a video stream into a file are different processes. That's why one tool doesn't handle both, and they're split by purpose.
There's a reason photos and videos are handled separately. A photo is complete as a single file, but video is often served as a streaming format split by quality level, so it takes a separate step to stitch it back into one downloadable file. The way this tool assembles photo addresses and the way the video tool works are different by design from the start.
Photos from private (locked) accounts and deleted posts can't be retrieved this way either. The syndication API only returns public tweets. If the account is locked or the post is gone, the API never hands over a photo address, so there's no way to get anything — original or reduced.
This isn't a limitation of this tool alone. As long as a service relies on the same syndication API, no photo downloader can retrieve photos from private accounts or deleted posts. The API simply doesn't return that data, so switching tools won't change the result.
Downloading several originals also means larger files. One or two photos is no big deal, but collecting a photo-heavy tweet or an entire thread at original resolution can add up to a lot of storage. And as noted, ZIP is store mode, so it doesn't shrink the size either.
To sum up, the quality gap comes from one thing. The address that displays a photo and the address that requests the original point at the same photo — the same family of URL — and the only difference is one parameter on the end. Once you know that, "it looks blurry" stops being Twitter deliberately making your photo worse. Display and archive were always managed as two different values.
Image quality and file size by saving method
The file you actually get depends on how you save it. The table below sums it up.
| Save method | What you actually get | Image quality | Handling multiple photos |
|---|---|---|---|
| Right-click on screen → Save image | Compressed copy meant for display | Low (blurry when zoomed in) | One at a time |
| Capture the screen (screenshot) | Exactly the size shown on screen | Depends on screen scaling | One at a time |
| Save button in the app's share menu | Often a compressed copy, depending on app settings | Low to medium | One at a time |
| Browser extension | Depends on how the program handles it | Varies by program | Requires installation |
| Editing the photo URL with the orig parameter | Uploaded original | Original | Manual repeat for each photo |
| Saving single photos with this tool | Uploaded original | Original | One click per photo |
| Checking several photos and saving as a ZIP with this tool | All selected photos, original resolution, uncompressed bundle | Original | All at once in one batch |
As the table shows, what decides "original or not" isn't the type of save button — it's whether the URL actually requested carried the orig parameter. Button names and save locations don't affect the result. It's also worth noting that methods whose inner workings you can't easily check, like extensions, give different results from program to program and are hard to generalize about.
Looking at the table again, if you only care about image quality, the three ways to get the original (editing the URL directly, saving single photos with the tool, and ZIP saving with the tool) all produce the same result. The only difference isn't image quality — it's how much manual work it takes when there are several photos.
Common places you get stuck
When you're using the tool, the places you get stuck are usually the same ones every time.
| Symptom | Cause | Fix |
|---|---|---|
| Still blurry after saving | Right-click saving pulled the compressed display copy as-is | Change the photo URL to the orig parameter and download again, or get the original with this tool |
| No photos at all after pasting a URL | Private (locked) account, or a post that's already been deleted | Only live posts from public accounts work, and there's no workaround |
| I want a video or GIF instead of a photo, and it won't work | This tool is photos only and doesn't handle video or GIFs | Use the "X (Twitter) Video Downloader" tool |
| Some photos were missing from the ZIP after I picked them with checkboxes | A check got cleared or skipped during selection | Select all, check the list again, and retry the ZIP save |
| Nothing happens when I press the ZIP button | The button was pressed with no photos selected | Check at least one photo, then press ZIP save |
| The ZIP file is bigger than I expected | It uses store (no compression), so originals are included as-is | That's normal — it actually means the originals are guaranteed |
| Fewer photos than expected from a tweet URL | Photos from other tweets later in the thread aren't included | Paste the URL of each tweet that has photos separately |
| No photos appear even though it isn't private or deleted | The tweet only has text or a poll | Double-check that the tweet URL actually has photos attached |
To sum up, "blurry" problems are almost always because you got a compressed copy, and "nothing shows up" problems are almost always because the account is private or the post was deleted. The two causes are completely different, so the same fix won't solve both. Either way, checking first whether the tweet URL is live and the account is public will narrow down the cause by half.
Can I use the photos I saved however I want?
All this tool can pull is photos posted in public tweets. For private accounts or deleted posts, there's no access path to begin with, so there's no way to get the photos.
And getting a photo at original resolution doesn't mean the copyright comes with it. The copyright still belongs to the person who first took and posted the photo. Downloading the original file and deciding where and how you're allowed to use it are two completely separate questions.
Saving photos you took and posted yourself, keeping them for personal use, or setting them as a wallpaper to look at on your own is generally not a problem. On the other hand, reuploading someone else's photo as if it were yours without crediting the original creator, using it commercially without permission, or passing the original file along to another account can lead to copyright infringement.
Quoting a tweet and introducing it is a different thing from pulling out just the photo file and posting it somewhere else. If you move only the photo without a link to the original post or a credit to the creator, you erase who first took and posted it, which can make the copyright problem bigger.
Sharing a screenshot of the whole tweet and saving just the photo file to use separately are also different. A screenshot carries the tweet's author and date along with it, so the source is relatively clear, but once you pull out just the photo file, those traces disappear — which means you need to be more careful when redistributing it.
In particular, cropping out a watermark or account name from a photo and reposting it can be treated as an entirely different matter from simply saving a photo for your own personal collection. Remember that getting the file at original resolution doesn't mean you've been given permission to redistribute it.
The rules don't change just because an account is an official organization. Before you download a photo, check whether that account has a separate statement about how its photos may be used, and if it doesn't, it's safer to limit your use to personal, non-commercial purposes.
If you're downloading photos from your own tweets later to back them up, there's nothing to worry about. Conversely, the more a photo comes from someone else's account, the safer it is to keep your use of it after saving on the conservative side.
In fan communities that follow these accounts, it's common to save original photos for personal collections and enjoy them or compare image quality with each other. That kind of use is rarely a problem, but the moment you make those photos into merch or products and sell them, it becomes a completely different matter.
How this differs from other saving methods
If you search for ways to get Twitter photos in original quality, you'll see plenty of instructions to install a browser extension. Extensions work by giving your browser extra permissions, so you have to keep track of installing and updating them, and if you switch browsers you have to install them again.
There are also general-purpose downloader sites that support several social networks at once. The advantage is that they work across platforms, but some of them don't add the original parameter to the photo URL and just pull the shrunken URL shown on screen, so the only way to know whether you actually got the original is to download it and check the file properties. Because they try to cover many platforms at once, they seem to end up missing the parameter rules specific to Twitter photos.
Screenshot apps and screen capture features are convenient in that they need no installation and can capture any screen, but as explained earlier, they capture exactly the pixels shown on screen, so they have nothing to do with the actual resolution of the original file. No matter how much you zoom in before capturing, the pixel count of the file itself doesn't increase. If anything, screen scaling and device resolution get mixed in during the capture, which adds yet another compression step on top of the original.
It's also different from Twitter's official "Tweet embed" feature. An embed is a way to set a tweet into another website as a card, not a way to download the photo file itself to your computer. If you want the photo as an actual file, you need a saving process like this one, not an embed.
Some people open the Network tab in developer tools and find the photo URL by hand. The principle is the same as the URL editing described earlier, but it's limited to people who know the method and know how to use it. This tool is close to taking that process and turning it into a few buttons on screen.
It's also different from the "Save photo" feature built into mobile apps. The built-in app feature works right away with no setup, but its structure saves the display file as-is, so it doesn't guarantee original resolution.
There are similar services that require signing up or paying, but this tool offers the same capability free, with no signup or payment.
The simplest method is to ask the original poster for the original file directly, but it can take time to get an answer, or you may never get one at all. This tool is practical in that, for any public photo, you can check the original right away without going through that.
This tool differs from the methods above in that you don't install anything — you paste a URL, and it automatically adds the original parameter for photos and fetches them, and for multiple photos you can pick them with checkboxes and build a ZIP in one go.
The Bottom Line
- The photos you get from the Twitter timeline and the Save button aren't the uploaded originals — they're shrunken display versions.
- Strip the extension off the end of the photo URL and add the
format=jpg&name=origparameter, and you get the original resolution. - When we checked with photos from NASA's official Artemis account, all four originals were 5568×3712.
- You can pick multiple photos with checkboxes and save them on the spot as a single uncompressed ZIP, right in your browser.
- Tweets with GIFs or video, private accounts, and deleted posts can't be saved this way.
Free · No login needed · Select multiple photos and save them all as a ZIP in original resolution at once
Frequently Asked Questions
Why do Twitter photos save so blurry?
Because the photo on your screen is not the uploaded original — it's a shrunken copy Twitter compressed for display. Right-click saving and the app's Save button both grab the file that's on screen, so changing how you save won't change the result. To get the original, you have to add a parameter to the photo URL itself that asks for it. This isn't some special Twitter policy; it's a common way websites serve images so they pop up fast on screen.
How different is a right-click save from the original, really?
It varies by photo, but when we analyzed photos from NASA's official Artemis account, the originals were 5568×3712. The shrunken version you see in the timeline is scaled way down to fit your screen, so the gap becomes obvious once you zoom in or print. Original resolutions differ from photo to photo, so when you save from another tweet, the accurate way is to check with this tool directly.
Can I download several photos at original quality at once?
Yes. Check the photos you want from the list, hit Save ZIP, and every selected photo comes down in one archive at full original resolution. The archive is built right there in your browser and isn't stored on any server. You can uncheck freely, so you only grab the photos from a tweet that you actually need.
Can I save photos from a private (locked) account?
No. The API that fetches photo URLs only responds for public tweets, so if an account is locked, there's no path to the photos — not with this method, not with any other. Deleted posts are just as inaccessible. This is a limit of how the data is accessed, not a policy, so don't expect a workaround down the road.
How do I save a tweet with a GIF or video attached?
This tool handles photos only. If a tweet has a GIF or video attached, the processing path is different, so this tool doesn't deal with it and points you to the "X (Twitter) Video Downloader" instead. For tweets that mix photos and video, you'll need to use each tool separately. It's a bit of extra work, but it's the result of splitting them up so each tool works more accurately for its format.
Can I repost photos I saved at original quality on my own social media?
Getting the original resolution doesn't transfer the copyright. The copyright stays with whoever posted the photo first. If you took the photo yourself or you're keeping it for personal use, there's little issue, but reuploading without credit or using it commercially can amount to copyright infringement. Removing watermarks or account labels before reposting can be an even bigger problem.
How do I check that a saved photo is really the original?
Open the saved file and check the pixel dimensions in its properties or info panel. If you saved it with this tool, the resolution shown on screen (say, 5568×3712) should match the pixel size of the actual file. If the numbers differ, it got compressed somewhere else along the way. On Windows, check the "Details" tab in file properties; on macOS, check the Get Info window.
This article was adapted from our Korean original. Read the Korean original