What Happened to Twitter Moments? Current Alternatives
Revive.Social Editorial X Moments (formerly Twitter Moments) were curated collections of posts arranged into a story. Most users can no longer create them: the official support account announced the removal of Moment creation on December 7, 2022.[1]
That is why an old “create a Twitter Moment” guide may send you to a missing menu or a page that no longer works. This refresh explains what Moments were, what may remain viewable, and how to rebuild the same editorial job with a thread, List, eligible long-form X Article, or website recap. 🧭
What were Twitter Moments?
On X, a Moment gathered selected posts into an ordered collection with a title, description, and cover. Instead of asking readers to follow a scattered conversation, the creator could choose the important items and put them into a beginning, middle, and end.
The format was useful for event recaps, developing stories, reactions around a topic, and collections of posts from several accounts. X also curated Moments, while eligible users historically created their own collections. Those workflows should now be treated as product history rather than current instructions. 🗃️
A Moment did more than save links. The editor selected context and order, which meant the collection could shape how a reader understood other people’s posts. X’s historical Moments principles emphasized accuracy, context, attribution, and avoiding misleading presentation.[2] Those responsibilities remain useful for any replacement format.
The original tool also solved a discovery problem: a reader could follow one curated narrative without knowing every account involved. Replacements divide that job differently. A thread emphasizes the publisher’s own sequence, a List emphasizes accounts, and a blog recap can mix sources with longer editorial context.
That distinction matters when someone asks to “recreate a Moment.” First identify whether they need a fixed story, a live monitoring feed, a long explanation, or an owned archive. Rebuilding the old interface is not the goal. Preserving the reader’s job is. 🎯
Can you still create an X Moment?
For most users, no. The product removal announcement is the load-bearing source, and the former English creation route returned a 404 during the August 2026 audit. A missing profile menu or creation button is therefore not a problem that a new device or account setting is expected to fix.
Do not follow an old workflow that tells you to open Moments from a profile menu, select posts, choose a mobile cover, and publish. Those steps describe a retired user-creation tool. They may still appear in search results or translated documentation, but that does not make the feature available. 🚫
This answer is deliberately qualified as “most users.” It does not claim that X has no internal or privileged curation workflow. It means ordinary readers should not plan a campaign around public Moment creation unless X publishes a new current announcement and the control can be verified in the intended account.
What happens to previously created Moments?
When creation was removed, X said people could still view previously published Moments. That statement describes the transition at the time, not a permanent availability guarantee for every old URL. An individual collection may later become unavailable because the feature changes, a source post is deleted, an account becomes protected, or the collection itself disappears.
If an old Moment matters to your organization, open it while signed out as well as signed in, record the source URL, and inventory the posts and context you have the right to reuse. Do not assume that copying screenshots or another person’s media into a new article is allowed merely because it appeared in the collection. ⚖️
For durable material, rebuild the editorial narrative on a property you control and link to the original posts. Keep a source list and note when a post was viewed, because deletions or later edits can change the meaning of the collection. Use quotations sparingly and preserve the speaker’s context.
Take a structured inventory before the old collection disappears. Record the Moment URL and title, each source post URL, account name, publication order, your own connecting text, and any media whose rights need review. A list of links is safer than a folder of downloaded images with no provenance. 📋
Decide what not to preserve. Remove a post when its author deleted it, the account became protected, the claim was corrected, or the item no longer supports the narrative. If the omission changes the conclusion, add an editorial note rather than silently presenting the rebuilt collection as identical.
For an organizational archive, assign an owner and review date. The owner should check source availability, attribution, alt text, quotations, corrections, and links. A durable webpage needs maintenance precisely because it outlives the fast-moving conversation it summarizes.
Why old Help Center instructions are misleading
Documentation can lag behind a product. During the August 2026 review, the English creation route was unavailable while a localized French Help page still displayed the former creation workflow.[3] The conflict is evidence of stale instructions, not evidence that user creation returned.
When sources disagree, prefer a dated official product announcement plus the behavior of the current product over an undated translated tutorial. Also check whether the page names old branding, old menu labels, or a route that does not exist in the current account. 🔍
- Check the date: Does the source predate the December 2022 removal?
- Check the locale: Do English and translated pages describe different products?
- Check the route: Does the linked creation page load and match the current interface?
- Check the account: Is the control actually present for the account expected to use it?
A screenshot from 2018 or 2021 proves only that a control existed then. It should not be used as a current navigation aid. The same caution applies to claims about sponsored Moments, Explore placement, audience size, analytics, following a Moment, or a fixed number of posts. None belongs in a current guide without current primary evidence.
Current alternatives: threads, Lists, Articles, and blog roundups
Use a thread for a sequence
An X thread connects posts from one account into a sequence.[4] It fits a short argument, event summary, or step-by-step explanation. Put the main conclusion in the opening post, keep each item understandable on its own, and end with a source or next action.
Use a List for ongoing monitoring
An X List groups accounts into a dedicated timeline.[5] It works when the value comes from following sources over time rather than arranging individual posts into a finished story. Name the List clearly and review its membership so it does not become a stale directory. 📚
Use an Article when the account is eligible
X says publishing Articles is currently available to Premium and Premium+ subscribers, Premium Businesses, and Premium Organizations.[6] Verify eligibility in the publishing account because access can change, and do not make an Article the only archive when long-term ownership matters.
Before choosing an Article, confirm that collaborators can draft, review, and maintain it in the intended account. If those controls are unavailable, use an owned webpage instead of building a process around access that only one subscriber has.
Use a website recap for ownership
A blog roundup gives you control over headings, context, accessibility, corrections, and internal links. It can embed or link to source posts while adding an editorial explanation. The tradeoff is maintenance: you must review rights, replace unavailable sources, and keep the recap accurate. 🏠
Use permanence, participation, and editorial control as the main decision criteria. A thread is easy to share inside X but remains platform-dependent. A List updates continuously but does not create a finished narrative. An Article may support depth for eligible accounts, while a website recap gives the publisher the most control and the largest maintenance obligation.
Consider accessibility as well. Threads can become difficult to navigate when replies split the sequence, and Lists provide little narrative explanation. A maintained webpage can add headings, descriptive link text, image alternatives, corrections, and a clear source list. ♿
For a live event, a two-stage approach may work best: publish a short thread during or immediately after the event, then point it to a reviewed website recap. Label the recap as the maintained version so corrections do not fragment across several competing collections.
How to rebuild a curated story with current tools
1. Collect the source posts
Save the strongest original posts, their authors, dates, and URLs. Remove duplicates, screenshots without a source, and material whose ownership or context is unclear. For a developing story, note what was known at each point rather than rewriting the timeline with hindsight.
2. Choose the container
Use a thread for a compact sequence, a List for continuing observation, an Article for eligible long-form publishing inside X, or a website recap for durable editorial control. If two formats are needed, choose one as the canonical version and link the other to it. 🧱
3. Add context and attribution
Explain why each item matters and how it connects to the next one. Attribute the original speaker, distinguish fact from interpretation, and avoid using a reply outside its conversation. The X business account guide provides broader account context, but it does not restore Moments.
4. Publish and maintain
Preview links, check media permissions and alt text, then publish. Revisit the collection when sources are deleted, facts change, or a later post corrects the record. A curated story is an editorial product, not a one-time dump of links. 🔄
Twitter Moments are no longer a dependable creation tool, but the underlying job still matters. Choose a current format, preserve the original sources, add honest context, and own the maintenance plan before asking readers to trust the collection.
Before migrating a business archive, run one small example through the complete workflow. Check how deleted posts, long media descriptions, protected accounts, corrections, and mobile reading behave. If the replacement loses essential context or rights information, change the format before converting the remaining collections. A test migration is easier to correct than a large archive built on the wrong assumptions. 🧪
References
- [1] X Support announcement on Moment creation
- [2] X Help: Moments guidelines and principles
- [3] Stale localized X Help page for creating a Moment
- [4] X Help: How to create a thread
- [5] X Help: About X Lists
- [6] X Help: About Articles
