What Is a .JPG-LARGE File?
A .jpg-large file is an ordinary JPEG photo. Nothing is broken and nothing is corrupted — the file just picked up an extension that Windows doesn't recognise on its way out of Twitter/X.
by Robert Castillo · Published
The short answer
Rename the file. Change photo.jpg-large to photo.jpg and it will open in absolutely everything, because it was already a JPEG the whole time. Windows will warn you that changing the extension may make the file unusable — in this case it does the opposite, so click yes.
If you'd rather not rename anything, drop the file into the viewer on this site: it reads the actual contents instead of trusting the extension, so it opens straight away.
Where the file came from
Twitter — now X — serves each uploaded photo at several sizes, and the full-resolution one lives at a URL ending in :large. For years, right-clicking that image and choosing «Save image as…» handed the browser a filename ending in .jpg:large, and because a colon isn't allowed in Windows filenames it got saved as .jpg-large instead.
So the extension isn't a format at all. It's the size label from the URL that ended up glued to the filename. You'll see the same thing with .jpg-medium, .jpg-small, .jpeg-large and occasionally .png-large — all of them are the plain format they claim to be, with a suffix nobody intended you to keep.
It comes from X/Twitter
Saved from a timeline, usually by right-clicking the full-size image.
The contents are a JPEG
Byte for byte a normal photo. The extension is the only thing that's odd.
It isn't a virus
An unfamiliar extension isn't a threat by itself, and this one is just a naming accident.
How to open it, from quickest to most thorough
Open it here
Drag the file onto the viewer on this site. It looks at the file's real contents, so the extension is irrelevant and nothing gets uploaded.
Rename it to .jpg
On Windows, turn on «File name extensions» in the View tab of File Explorer, then edit the name so it ends in .jpg. On Mac, click the name once and edit it in Finder.
Open with an app that ignores extensions
Most image editors will open it regardless: GIMP, IrfanView, XnView and Photoshop all read the file header rather than the name.
Renaming is the permanent fix, and it costs nothing. Once the file ends in .jpg, Windows Photos, your phone's gallery, email attachments and every website will treat it like any other picture.
Why Windows refuses it in the first place
Windows decides what to do with a file almost entirely from its extension. There is no program registered for .jpg-large, so instead of looking inside the file and noticing it's a perfectly standard JPEG, it shrugs and offers you the «How do you want to open this file?» dialogue.
Macs behave better here — Preview and Quick Look usually open a .jpg-large without complaint, because macOS inspects the file's contents as well as its name. That's why the same photo can be unopenable on a PC and completely fine on a Mac.
Does renaming lose quality?
No. Renaming a file changes the label, not the contents: not a single pixel is touched, the file size stays identical and nothing is re-compressed. This is the one case where you get a fix for free.
What would cost you quality is opening the photo in an editor and re-saving it as a new JPEG, because JPEG is lossy and every save throws a little detail away. If all you need is for the file to open, rename it and stop there.
Stopping it from happening again
X has changed how it serves images more than once, and the modern URLs use a query string — ?format=jpg&name=large — rather than the old :large suffix. On those, «Save image as…» hands you a clean .jpg and the problem never appears. If you are still collecting .jpg-large files, you are most likely saving from an older cached page, an archived link or a third-party client that still builds the old style of URL.
The reliable habit is to open the image on its own first — click it so it fills the screen, then use «Open image in new tab» — and save it from there. The address bar shows you exactly what you are about to download, and you can strip anything after the file extension before saving.
It is also worth knowing that the mobile apps do not have this problem at all: saving a photo to your camera roll from the X app produces a normal image. This is strictly a desktop-browser quirk.