X gives you no button to save a tweet as an image, and its help centre has never documented one. Every route you will find is either your own operating system or a third-party tool, and none of them is X’s.
What X does publish is a set of rules for what a post has to look like once it leaves the platform. Those rules live in the developer terms under Display requirements, they are short, and almost nobody writing about screenshots has read them.
What X publishes instead of a way to save a tweet as an image
The general principles are two lines long. Do “display real, unmodified posts from real accounts.” Do not “modify post text,” and do not “use mock ups of posts that don’t exist on the platform.”
That second prohibition lands hard on the tools that dominate the search results for this query. A generator that lets you type any name, any avatar and any wording into a post-shaped frame produces a mock up of a post that does not exist. X names that as a thing you should not do, in its own documentation, in a bulleted list.
Five things a picture of a post has to keep
The broadcast section is the closest X comes to describing a static image of a post, and it is specific. Show the user’s full name, the @username, the post text and the profile picture. Use the full text, not a fragment. Keep the X logo near the post for as long as it is on screen. Do not “delete, obscure, or alter the post content or identification of the user,” with hyperlinks the single allowed exception. Do not exclude the timestamp.
Count what a habitual crop throws away: the avatar, the timestamp, and the logo, all three of them, every time. Cropping to the words is the default instinct and it is the part people get wrong.
No screenshot tool adds the X logo for you. That step is manual, and skipping it is the most common failure I see in reposted images.
The embed is the route X asks for on a web page
For anything online, the documentation is blunt about its preference: X strongly encourages embedded posts and embedded timelines, published from publish.x.com, because an embed renders correctly on its own and fetches current X data without OAuth. The same option is described in the new user FAQ as a widget you drop on a blog.
An embed pulls live data, so it has nothing left to render once the post or the account disappears. A picture survives that and stops being verifiable at the same moment. You are choosing which of the two failures you would rather have.
When you want to keep the post rather than publish it
Bookmarks are the documented answer and they are private: X says they are “only viewable to you within your X account.” On the web and on Android you add one from the share icon, with Add post to Bookmarks. On iOS you open the post and tap the bookmark icon.
For your own posts there is a heavier and more permanent option. Under Settings and privacy, open Account, then Data and permissions, then Your X data. X sends a code to your email or phone, you confirm, and you request the archive. When it is ready you get an email with a download link, and clicking it while signed in gives you a .zip of your posts.
Sources
- X Developer Terms, Display requirements: Posts
- X Help Center, About Bookmarks
- X Help Center, How to download your X archive and Posts
- X Help Center, New user FAQ