How to edit a post on X (and the 8 types you can't)

#Quick answer

Editing a post on X takes four taps, but only on an X Premium account: open the post's three-dot menu, choose "Edit post", change the text, tap Update. You get up to 5 edits inside 1 hour, only on original posts and Quotes, and only from the device you posted from. X's help page also names eight post types it will not edit at all, including pinned posts and anything published through a third-party tool. Free accounts have no edit button.

Last updated: October 2026

On X (formerly Twitter) the edit button is real, but it is narrower than almost every guide on this query admits. It costs money. It expires. It is capped. And there is a documented list of post types that are outside it completely, which is the actual reason most people find the option missing. Below: the steps, the full exclusion list, the six reasons the button disappears, the place where X's own two documentation sets contradict each other, what an edit does to your post's underlying ID, and what you can still change for free.

#Can you edit a post on X?

Yes, with one condition: you need X Premium. The edit button does not appear at all on free accounts. If you open the menu on your own post and see no "Edit post" option, that is the first thing to check. Per X's Edit Post help page, the feature is limited to Premium subscribers and applies only to original posts and Quotes.

Editing is included from the cheapest tier up, which makes it the least expensive thing on the subscription to unlock: Basic runs $3 a month on the web. It is still a paid gate, and worth weighing against the free workarounds further down. For a lot of people, catching the typo before it publishes is worth more than the right to fix it for one hour afterwards.

#How to edit a post on X, step by step

On a Premium account, editing takes four taps:

1. Go to the post you want to change. It has to be your own post, and it has to be an original post or a Quote.
2. Tap the three-dot menu in the top right corner of the post.
3. Choose Edit post.
4. Make your changes, then tap Update.

Your updated version replaces the original in place, and the engagement comes with it. X states that you keep the engagement from past versions of a post you have edited, which is the entire point of editing rather than deleting. A "Last edited" button appears on the post afterwards, and anyone can open it to read the earlier versions.

Steps are identical in the iOS app, the Android app, and on x.com in a browser. The one thing that changes across platforms is price, because subscribing inside the iOS or Android app costs more than subscribing on the web thanks to app-store fees. If you are buying Premium mainly for the edit button, buy it at x.com.

#The eight post types X will not edit

This is the section that answers the question most people are really asking, and it is missing from nearly every page ranking for this query. X does not just impose a time limit. It excludes whole categories of post. Its Edit Post help page lists them:

Three of those deserve spelling out, because they are the ones that surprise people.

Pinned posts cannot be edited. Pin a post to the top of your profile and you have taken the edit button off it. That gives you an ordering rule rather than a limitation: write it, read it twice, then pin it. If you are setting up the post that greets every profile visitor, get the wording finished before you reach for pin a post on X.

Posts from a third-party service cannot be edited, and neither can posts via X Pro. If a scheduler published it, the edit button is not yours to use. X's developer documentation goes further and lists scheduled posts, Community posts and Collaborative posts as non-editable too. An earlier version of this page argued the opposite, on the reasoning that the API exposes an edit endpoint. That was wrong: the endpoint exists, and the post types above sit outside it regardless.

Threads are excluded as a type. The practical version of this rule is the one people hit: the moment you reply to your own post to extend it, the original is part of a thread and it locks, even inside the hour. Proofread the first post of a thread before you add the second.

#What an edit cannot fix, even on an editable post

X describes an edit as adding, deleting or correcting text, and rearranging and tagging media. Read that list closely, because the things missing from it are the things that trip people up:

• You cannot swap an image. Rearranging and tagging the media you already attached is in scope. Replacing it with a different file is not. Attach the wrong screenshot and no edit saves you, whatever your subscription tier.
• You cannot change a poll. Polls are on the exclusion list outright, so the wording and the choices are final the second you publish. Getting the options right the first time is most of the work of running a poll on X.
• You cannot fix alt text. Image descriptions are locked at publish time, which catches people who assume an edit covers everything attached to the post. See how to add alt text on X for the detail.
• You cannot edit after the window closes. There is no "edit anyway" for older posts at any tier.

Simple enough to remember: an edit fixes words. Anything else attached to the post is set at the moment you hit publish.

#X's own pages disagree on how long you get

Here is a discrepancy worth knowing about, because it changes how much slack you should assume you have.

X's help centre is unambiguous for the in-app feature: "Edit post is a feature that gives you a 1 hour window", and "you'll have the opportunity to make up to 5 edits within that 1 hour window."

X's developer documentation for the same feature states something different. Its Edit Posts page gives the time window as "30 minutes from original post", with the same 5-edit cap. Thirty minutes was the original figure when editing launched in 2022, so the likeliest explanation is a developer page that never got updated after the consumer window was extended. But it is X's own current documentation, which is exactly why it is worth flagging rather than quietly picking the friendlier number.

There is a way to stop guessing. The API returns an edit_controls object on any post, and it carries three fields: is_edit_eligible, editable_until as a timestamp, and edits_remaining counting down from 5. For a specific post, editable_until is the authoritative deadline. If you build on the API at all, read it rather than trusting either page. The practical advice for everyone else is simpler: treat the first half hour as the real window and you will never be caught out by the gap.

#Every edit creates a new post, and that has consequences

This is the most under-reported fact about editing on X, and it is structural. Each edit does not modify the post in place behind the scenes. X's developer documentation states that each edit creates a new post ID, and that the full set of IDs is exposed as edit_history_tweet_ids, oldest first.

Two consequences follow, and neither is obvious from the app.

Deleting any version deletes the entire chain. This is documented explicitly. You cannot delete the embarrassing first draft out of your edit history and keep the clean final version. It is all one object. If the original wording is the problem, the post goes or it stays, in full.

Engagement is attributed per version. X's docs state that each version of an edited post has its own metrics, attributed to the version that was visible when the engagement happened. Your totals survive the edit, which is what the help centre means by keeping engagement. But if you are reading X analytics closely on a post you edited mid-flight, the numbers are split across versions rather than pooled into one clean row.

Edit metadata only exists for posts created since 29 September 2022. Anything older has no edit history at all.

#Why "Edit post" is missing from your menu

If the option is not there, work this list in order before touching your app settings. Every one of these is a rule, not a bug:

1. The post is one of the eight excluded types. Thread, reply, promoted post, poll, pinned post, posted via a third-party tool, posted via X Pro, or a Subscriber post. This is the most common cause and the one almost nobody checks, because the exclusion list sits further down the help page than people read.
2. You already replied to your own post. Adding to your own post makes it a thread and freezes the original.
3. The window is up. Look at the timestamp, and assume the shorter of X's two published windows.
4. You have used all 5 edits. Open the "Last edited" button and count the versions.
5. Premium is not active on this account. In a multi-account setup this is the quiet one. Premium attaches to a single account, not to your device or your card, so switching profiles switches the edit button off if the other account is not subscribed. Confirm which account actually published the post.
6. You are on a different device than the one you posted from. X states this plainly: "You can only edit a post from the device you sent it from." Post from your phone on the way to a meeting, spot the typo on your laptop twenty minutes later, and the option is not there. Nothing is broken and your subscription is fine. You are on the wrong machine. X's own troubleshooting answer for editing problems is this rule and nothing else.

Only once all six are ruled out is it worth the generic app fixes: update to the current version, sign out and back in, then reinstall. Those resolve a stale client, but a stale client is far less likely than one of the six rules above.

#Everyone can see that you edited it

X made editing transparent by design. An edited post carries a visible "Edited" label, and anyone can tap into it to see the previous published versions. There is no silent edit.

That matters twice over. You cannot use editing to rewrite history after a post gets attention, because the receipts stay public and, as covered above, you cannot prune them either. And on a post that is already performing, heavy editing reads as suspicious to the people who engaged with the earlier version. Nobody cares about a typo fix. For a substantive change to something already spreading, a follow-up post is the honest move, since the correction is then out in the open rather than buried in a version log.

#What you can still change on a live post, free

The edit button is not the only lever on a post that is already up. These work on every account, with no subscription and no time limit:

• Who can reply. Open the post's three-dot menu and choose "Change who can reply" to move between Everyone, Accounts you follow, Verified accounts, and Accounts you mention, per X's About conversations page. The walkthrough is in how to change who can reply on X. Tightening the audience stops new replies from outside the group; it does not remove the replies already there.
• Whether it is pinned to your profile. Pin and unpin are free and reversible at any time. Just note the trade-off established above: a pinned post is not an editable post.
• Whether it exists at all. Deleting is always available. How to delete a post on X covers what disappears and what does not.

None of that rewrites your words. But if the real problem is a post drawing the wrong replies rather than a typo, reply controls solve it in one tap and the edit window is irrelevant.

#Undo post: the window before the edit window

Premium ships a second safety net that solves the problem the edit button only patches, and most people either never switch it on or cannot work out why their posts feel slow.

Undo post holds a post for a short countdown before anyone sees it. Per X's Undo Post page, it "gives you the option to retract a post after you send it, but before it's visible to others on X", and X is explicit that it is not an edit button. Tap Undo and you land back in the composer, where you can rewrite it, abandon it, or save it to your drafts. Tap Send now to skip the wait.

Default period is 30 seconds, and the per-type toggles plus the timer live under Premium settings: on the app, Premium then Preferences then Early access to select new features then Undo post; on x.com, Premium then the gear icon then Undo post.

Two things make this the more useful of the two features. It covers replies, threads and polls, every one of which the edit button excludes, so it is the only way to catch a typo in a reply. And because you are returned to the composer rather than to an editor, you can swap the image, which an edit cannot do at any tier.

It also explains a complaint that gets misdiagnosed as a bug: "my post did not appear right away." X's own FAQ answers that directly. As an active Premium subscriber you will not see a new post in your Home timeline immediately, because the Undo window is holding it. That is the feature working. Turn Undo post off in Premium settings, or tap Send now, if you would rather have the post go out instantly.

#No Premium? The free workarounds

If you do not pay for Premium, or the mistake is in a reply, or the window has passed, two honest options remain:

• Delete and repost. Delete the flawed post and publish a clean version. You lose the original likes and reposts, but the corrected version is the only one people see going forward. This was the default before the edit button existed and it still works fine on posts that have not gathered much engagement yet.
• Quote-post the correction. Quote your own post with a short note, "Fixed link below" or "Correction:", and the right information. That keeps the original's engagement visible, gives the correction its own distribution, and is transparent about what changed. It is the better choice when the original already has traction you do not want to throw away.

Neither is as clean as an in-place edit. Both are free, and both beat pretending the mistake never happened.

#The better fix: stop needing the edit button

Most of what the edit button fixes is a problem you can design away. Most edits are a last-minute typo, a broken link, or a wrong number, and all three are far cheaper to catch before publishing than to scramble over inside a window you cannot even pin down to the minute. Two habits remove most of the need for it.

Draft ahead instead of posting live. When you write in advance you read the post once more before it goes out rather than firing it off in the moment, and our guide to scheduling posts on X covers the free and paid ways to queue that up. Note the catch that now applies: a post a scheduler published is a post you cannot edit, which raises the cost of getting it wrong in the queue.

Then let something check the post before it publishes. X-Autopilot drafts posts and replies in your voice from real Chrome on your own Mac, so problems surface at the draft stage instead of during a race against the edit clock. Be clear-eyed about what that is: browser-route automation on X is a gray area rather than an approved path, and running locally on your own session is a smaller detection surface than a cloud tool posting from a shared IP pool, not an absence of risk. It also will not turn a weak post into a good one. What it removes is the friction that produces the typos you would otherwise pay Premium to fix.

The edit button is genuinely useful the day you need it. It is a safety net with eight holes in it, not a workflow. The people who rarely reach for it are not faster typists. They just read the post one more time before it publishes.