Where are drafts on X? Find your unsent posts

Drafts on X are not on a page of their own. To find where drafts are on X, open the composer by selecting the Post button, then select Unsent posts at the top of the compose box. That screen holds two tabs, Drafts and Scheduled, and everything you saved without publishing is in the first one.

The reason people search for this at all is that the entry point is hidden inside the composer rather than in a menu, and the drafts themselves behave in a way nobody warns you about. They are stored on the device you wrote them on. Not on your account.

#How to find drafts on X

Same shape everywhere, with slightly different chrome.

On the web at x.com

1. Select the blue Post button in the left sidebar. The composer opens as a pop-up.
2. Look at the top right of that pop-up for Unsent posts.
3. Select it. You get the Drafts and Scheduled tabs.
4. Click any draft to load it back into the composer, finish it, and post.

On iOS and Android

1. Tap the compose icon, the floating button with the pen.
2. Tap Unsent posts at the top of the compose screen.
3. Choose Drafts.
4. Tap a draft to reopen it.

If you have never saved a draft on that device, the list is empty. An empty list is not evidence that your drafts were deleted. It is usually evidence that you wrote them somewhere else, which is the next section.

#How to actually save a draft

X does not autosave everything you type. The save happens at one specific moment: when you close a composer that has text in it.

Start writing, then close the composer with the X or the back arrow. A prompt appears asking whether you want to save. Select Save, and the text moves into Unsent posts. Select Discard and it is gone immediately, with no undo.

Two habits follow from that:

• Never close the browser tab to abandon a post. Killing the tab skips the prompt, and anything unsaved goes with it. Close the composer first, take the save prompt, then close the tab.
• Save early on long posts. If you are drafting a thread, save once when the first two or three posts are down. A saved draft can be reopened; a composer that crashed cannot.

#The rule nobody tells you: drafts are local

This is the part worth internalising, because it explains almost every drafts problem people have.

X holds drafts in local storage on the device and in the specific app or browser where you created them. They are not attached to your X account and they do not sync. Concretely:

So the answer to "why can I not see my drafts on my other device" is that the draft never left the first one. Nothing is broken and support cannot restore it.

Media makes it worse. Even in the cases where text appears to carry across a session, attached images and video generally do not, so a draft you reopen can come back as the caption without the picture. Check the attachment before you post rather than after.

#Why your X drafts disappeared

Every common cause is a variation on the same thing: local storage got cleared.

• You logged out of the app. Signing out clears local app data on many builds, drafts included.
• You cleared the app cache or storage in your phone's settings.
• You deleted and reinstalled the app. A reinstall starts from an empty container.
• You cleared cookies and site data in your browser, or ran a cleanup tool that did.
• You were in a private or incognito window. That storage is discarded when the window closes.
• You switched browsers. Chrome and Safari keep separate storage, so the draft stayed in the first one.

There is no recovery path for any of these. X does not hold a server copy to restore from, and there is no export. If a draft mattered and it is gone, it is gone.

A practical response is not to be more careful. It is to stop keeping anything valuable in drafts.

#Drafts versus scheduled posts, which is the real distinction

Both tabs live under Unsent posts, and that shared home hides how differently they work.

A scheduled post is stored on X's servers. It shows up under the Scheduled tab on every device you sign in to, it survives a phone wipe or a browser reset, and it publishes at its time whether or not your device is on. To make one, write the post, select the calendar icon at the bottom of the composer, pick a date and time, and confirm. Native scheduling on X does not require a paid subscription.

A draft is a note to yourself, held on one machine, that you have to be present to publish.

That gives you a simple rule. If you would be annoyed to lose it, schedule it instead of drafting it, even if the time you pick is arbitrary and you plan to edit it later. You can open anything under the Scheduled tab to change its text, its media, or its time, or delete it before it sends. The scheduled version costs you nothing extra and it is backed up by definition.

Our walkthrough of scheduling posts on X covers the native flow and the third-party routes side by side, and if the reason you are drafting is timing, the best time to post on X has the windows worth aiming at.

#Cleaning up the drafts list

Old drafts pile up fast, and a list of forty half-finished thoughts is a list you stop opening.

To delete them, open Unsent posts, go to Drafts, and use Edit at the top right. Select the drafts you no longer want and confirm the deletion. On mobile the same Edit control lets you multi-select. Deletions here are immediate and local, so there is nothing to undo and nothing to sync.

A reasonable rhythm is to clear the list monthly. Anything you have carried for a month unfinished is not a draft, it is an idea, and ideas belong in whatever you actually use for notes rather than in a composer you have to dig into a menu to reach.

#Where a serious posting queue belongs

A draft is fine for the post you will finish in ten minutes. They are a poor system of record for anything else, because the storage model was never designed to be one: no sync, no backup, no export, no shared access, and no visibility into what is queued.

If you are running an account with any regularity, the queue wants to live somewhere durable. Native scheduling covers most of that for free and should be your default. Beyond it, a dedicated tool adds the thing scheduling cannot do, which is the engagement side of the account rather than the publishing side. Our comparison of X-Autopilot and Buffer sets out where a scheduler stops and an engagement agent starts, and X-Autopilot itself runs from your own Mac and your own logged-in session rather than a shared cloud account.

Whatever you use, the takeaway for drafts is small and firm. Open the composer, select Unsent posts, and expect to find only what you wrote on that device. If it matters, schedule it.