If Twitter archive images are not loading, first check whether the image file exists locally. A broken viewer link, an incomplete extraction and a missing attachment require different responses. Keep the original ZIP unchanged and investigate a separate extracted copy.
This guide starts after you have downloaded an account archive. If you still need the ZIP, follow how to download and open your archive. The steps below help you describe a media gap accurately. They cannot recover a file that no available source contains.
Identify what is actually failing
Open the included HTML viewer from the extracted folder, if your archive includes one. Check a post with a missing image and another post whose image works. Note the post IDs, archive download date and what appears: a blank area, broken-image symbol, thumbnail or error message.
| What you find | What it suggests | Next check |
|---|---|---|
| No posts or interface controls load. | A wider viewer or extraction problem. | Re-extract the complete folder before investigating individual attachments. |
| The image opens as a local file but not inside the viewer. | The file exists; the viewer is not displaying it. | Check the viewer's folder location and resource path. |
| The image is listed in the ZIP but absent from the extracted folder. | The extraction did not produce that file where expected. | Check extraction errors, destination and available storage. |
| A record references media, but no corresponding local file is found. | The record and the saved attachment may have different coverage. | Check the ZIP listing and another preserved snapshot. |
| The attachment opens only from an online address. | You have an online reference, not a verified offline copy. | Record the URL and whether an accessible local copy exists. |
These are diagnostic clues, not proof of a particular X export defect. Several faults can produce the same broken-image symbol.
Check the extracted folder before changing files
- Keep the ZIP in its original location. Create a new working folder with a clear account and snapshot label.
- Extract the entire archive into that folder. Watch for an extraction error or skipped files.
- Open the HTML entry point from that extracted copy. Opening an HTML preview inside a ZIP is not the same check.
- Leave its companion data and asset folders in their original relative positions. Do not move only the HTML file to the desktop.
- Try a current browser with that same complete folder. Record whether the behavior changes.
Relative resource references depend on their base location, as MDN explains for URL resolution. Applying that principle to a local viewer explains why moving its entry file can break resource links. It does not establish that every archive uses the same folder names or reference format.
Do not rename all media files, remove folders or edit the original viewer as a first fix. Those changes can create a second problem and make the original failure harder to identify.
Trace one missing attachment
Choose one affected post instead of searching blindly through every photograph. Save its exact ID as text. In a working copy of the post-data files, find that ID with a text editor. Our archive format reference explains the JavaScript wrapper and split data files. Read these files as data; do not paste their contents into a console or execute them.
Inspect any media objects that the record actually includes. Depending on the export, these can provide an attachment ID, a filename or a remote URL. These are different identifiers. A post ID need not be the image's filename, and an online address does not prove the image bytes were downloaded.
Use the archive's actual names and references to search the extracted media folders. Open a plausible file directly in an image viewer and compare its content. A matching name alone is weaker than a matching reference and the expected picture.
If you are comfortable with browser developer tools, you can also inspect the failed image's requested address. Compare that address with the actual local path. Avoid sharing an unredacted screenshot of developer tools: it may reveal private filenames or account data. Do not disable browser security settings to make an unknown viewer work.
Compare the ZIP with the local files
If the expected file is absent after extraction, inspect the ZIP's contents without altering it. An archive utility's file list can show whether that member exists before you extract it again. Search the actual media filename or a distinctive part of it, not just the post's text.
- Present in the ZIP: try a fresh extraction into a new destination. Keep the extraction error if it fails again.
- Absent from the ZIP: another extraction cannot create it. Check a separately preserved archive or an original photo you already own.
- Present but cannot open: record the file size and error. A file can exist without being a usable image.
- No clear filename mapping: mark the attachment as unresolved. Do not label it absent solely because a filename search failed.
X describes account archives as including media among the account information supplied. That description is not a verification that a particular attachment exists in your downloaded ZIP. Inspect the copy you received.
A worked check: viewer error or absent image?
Consider an illustrative archive with two affected posts. For the first post, its picture opens from the extracted media folder. The HTML viewer was copied to a different directory. Opening the viewer from a fresh, complete extraction displays that picture. The check supports a folder-path explanation for this case; it does not require downloading the picture again.
For the second post, the data contains an online media address, but you cannot identify a matching local file in either the extracted folder or the ZIP listing. An older preserved archive contains a matching picture. Keep that older source and its snapshot date. You can use its copy in a separate research collection, but do not describe the newer ZIP as complete or overwrite it with a repaired version.
Both examples are illustrative, not tests of a real user's archive. If no preserved source contains the image, state that limit. An inaccessible online URL is not a recovered attachment.
Record the result and share a narrow copy
For each checked attachment, keep a short note: post ID, source ZIP, snapshot date, reference or filename, checks performed and result. Use specific outcomes such as “opens locally; viewer link fails,” “listed in ZIP; extraction failed” or “mapping unresolved.” These are more useful than calling every gap “missing media.”
Check more than one post before treating a fix as archive-wide. Include an early post, a recent post and different attachment types that your archive contains. A photo that opens does not verify every video or Direct Message attachment.
Keep account archives private. They can contain messages and account details unrelated to your task. Share the selected attachment and its source note instead of the full ZIP. If the question concerns a deleted post, use the separate deleted-post evidence checklist; fixing a viewer cannot restore a deleted original on X.