Short answer
Paste the tweet link into PeekVault's tweet viewer and the official embed renders it without login. If the embed fails because the tweet was deleted or the account is protected, the viewer shows the latest Wayback snapshot of that URL when one exists.
Open the tweet viewerWhy X shows a login wall
Since mid-2023 X has treated logged-out visitors as a cost. Profiles, timelines and search went behind login first. Single tweet pages came next, but not all at once. X tests different behaviors on different visitors, so one person sees the tweet and another sees the sign-in prompt for the same link on the same day.
On a phone the link often tries to open the X app instead. If the app is not installed, or you are not signed in there, you land on the web login page. None of this means the tweet is gone. It means the tweet page and the login wall are the same page for logged-out visitors.
Method 1: paste the link into the tweet viewer
PeekVault's tweet viewer takes any tweet URL, from x.com or twitter.com, and asks X's embed endpoints for the tweet. If X serves it, you see the author, the text, images or video, the date, and a link back to the original. That is the whole tool. It never logs in, never scrapes a timeline, and never stores what it showed you.
Copy the link from the message you received, open the tweet viewer, paste, and press open. If the link came with tracking junk after a question mark, leave it. The viewer strips it. If the link is a t.co short link, open it in your browser first, then copy the x.com address it lands on.
Method 2: use the embed endpoint yourself
You do not have to go through PeekVault. X publishes an endpoint at publish.twitter.com/oembed. Put the tweet URL after url= and load it in a browser. The response includes a block of HTML. Save that block into any web page, or into a local file that ends in .html, and open it. The tweet renders, complete with the author's avatar and any media.
This is the mechanism behind every embedded tweet you have seen on a news site. X keeps it running because publishers depend on it. That makes it far more stable than any scraping mirror, and it is the reason PeekVault built the tweet viewer on top of it instead of on a copy of Nitter.
When the embed fails
The embed fails only when X will not serve the tweet to anyone logged out. A well known example is the covfefe tweet from May 31, 2017. Its author deleted it a few hours after posting, so the embed endpoint returns nothing for that URL. Yet you can still read it, because the Wayback Machine captured the tweet page before the deletion. The same pattern applies to most tweets that made news and then vanished.
When the tweet viewer gets an empty response, it tells you which of these cases is likely.
- Deleted: the author or X removed the tweet. Only a snapshot can show it now.
- Protected: the account is private. Embeds never work for protected accounts, and no snapshot exists either.
- Suspended: the account was banned. Embeds fail, but snapshots from before the suspension often exist.
- Age-restricted or sensitive: X hides some media from logged-out visitors. The text may still render while the image does not.
- Rate-limited: X throttled the embed endpoint for a few minutes. Wait and retry. Nothing is wrong with the tweet.
Fallback: read the snapshot
When the embed comes back empty, the viewer checks the Internet Archive for captures of the same tweet URL. If any exist, it opens the latest one inline and shows the capture timeline, so you can step back to an earlier version if the latest one already shows a deletion notice.
Snapshots are not embeds. They show the tweet page as X served it on that day, which may include the old design, a login banner, or a partially loaded thread. The text of the tweet is what matters, and it is usually there. If no capture exists, the tweet is not readable without an account, and PeekVault says so rather than guessing.
Tips for links on a phone
Long-press the link in your messaging app and choose copy instead of tapping it, so the X app does not grab it. Paste it into the tweet viewer in your browser. If a friend keeps sending twitter.com links, they still work. The viewer treats twitter.com and x.com as the same address.
FAQ
Straight answers
Will the author know I opened their tweet?+
No. An embed request goes from your browser to X's embed servers, the same as loading a news article that quotes the tweet. X does not tell the author who viewed an embed, and PeekVault sends nothing to the author.
Why does the same link open one day and not the next?+
X tests its login wall on a share of logged-out visitors and changes that share often. Your browser, your region, and whether a cookie from an old session survives all affect it. The embed route does not have this problem.
Can I read the replies under the tweet?+
Not through the embed. It renders the single tweet, and the parent tweet if it is a reply. Reading a full reply thread requires login on X. A snapshot of the tweet page sometimes includes the first replies as they loaded that day.
Can I open a tweet from a protected account?+
No. Protected accounts are never public, so X does not serve embeds for them and there are no snapshots. Only followers approved by the account can see those tweets.
Is using the embed endpoint allowed?+
Yes. X publishes it for exactly this purpose and every major news site uses it. You are reading a public tweet the way X intends embeds to be read.
Does the tweet viewer cost anything or need sign-up?+
No. It is free, there is no account, and there is no limit on how many links you paste.
Why does a Nitter link my friend sent not work?+
Most Nitter instances went offline in August 2026. Replace the Nitter domain in the link with x.com, keep the rest of the path, and paste the result into the tweet viewer.
Keep going