How to archive tweets permanently

Authors delete posts, accounts get suspended or locked, and a public account can switch to protected. Any of those turns a bookmark into an empty row. The URL still looks like an address. It just does not resolve to the words you remembered.

That is a property of the product, not a glitch. X bookmarks, likes and embedded timelines all point at the live post. If you need the post after that, you have to have stored the content somewhere X does not control.

X will give you a download of your account. Open Settings and privacy, then Your account, then Download an archive of your data, confirm it is you, and request it. X builds the file and notifies you when it is ready. It is not instant, and the link does not stay up forever, so download it when the notice arrives.

The archive is the right backup of your posts, media and account history as of that day. It is a snapshot: posts you write afterwards are not in it until you request another one, and a post you delete before the next request is gone. It is also not a bookmark export. What it leaves out is covered in how to export Twitter bookmarks.

You cannot request someone else’s data download. For a public post, three copies are realistic. The Wayback Machine (web.archive.org/save) stores a public snapshot of the URL, if the site allows it. Print to PDF stores a private file of what you see. A full-text tool stores the words and images in a library you can search.

All three have to happen while the post is public. After a deletion, the chance of a new copy drops to whatever was already archived. If seeing deleted posts is the actual problem, start with how to see deleted tweets.

A screenshot is honest and immediate. It shows the post as you saw it, including the layout. A year later it is an image in a camera roll: no search, no author field, no link back unless you typed one into the filename.

A full-text archive stores the words as words. You can search a phrase, keep the author and the URL beside the text, and still read it if the URL dies. You give up the exact pixels. For almost every “what did they say about this?” question, the text is the thing you wanted.

A thread is a chain of posts, and most save buttons act on one URL. Archiving the first post does not archive the replies under it. Unroll sites can show a public thread on one page while the posts are still up. They are not a private backup, and they go blank when the posts are deleted.

To keep a thread, save the posts that carry it — the ones with the claim, the numbers, the images — not only the opener. The trade-offs are on how to save Twitter threads.

Tweets are news-shaped. The useful question is often “what was being said that week?”, not “which folder did I drop this in?”. A date is already on the post. An archive that files the save on the day you made it lets you open that day and see the posts next to the articles you saved with them.

Folders still help for topics. They are a poor index for time. WHT.day’s personal news archive is built as a calendar: each save lands on a day, search runs across every day, and the night’s saves are also written up as a digest.

This is not a background sync of your X account. Nothing is copied until you ask. On a post you have open, the browser extension saves that post’s text, author and images into your archive. You can also paste the URL. If you already have a list of links, Import on your account will try them — up to 500 at a time — and can only fetch posts that are still public.

The nightly digest is the part that happens on its own: the day’s saves are turned into a front page and filed. The capture stays a choice you make while the post exists.