What happened to Beeper and Texts.com?

The change was a sequence, not a single shutdown. Automattic bought Texts.com in October 2023; the October 24 acquisition report dates the deal. On April 9, 2024, Automattic announced its purchase of Beeper and said the two products would merge under the Beeper brand. At that point, it explicitly told people to keep using both apps while it worked out a phased plan.

On February 24, 2025, Beeper released redesigned desktop and iOS apps in beta. The desktop rewrite used the foundations of the Texts desktop app; the iOS app was built anew. On July 16, 2025, Beeper introduced on-device connections and paid tiers. That was a product change, not evidence that every existing Beeper Cloud connection instantly moved to a device.

Today the Texts home page calls Beeper the next generation of Texts, says the teams, products, and technology merged, and asks users of the original app to try Beeper for more frequent updates. It also says an existing Texts subscription includes Beeper Plus features. That gives a practical answer to “is Texts gone?”: the brand and older app have not simply vanished, but Beeper is the product to evaluate for current development.

Texts had a distinct approach: its own FAQ describes an app that runs on macOS, Windows, and Linux and keeps message data on the device. Beeper’s February 2025 desktop rewrite drew on that desktop foundation, while the later Beeper release added on-device connections to the combined app. The result is not a simple rename of the old executable. A Texts user should test the current Beeper app with the same accounts and habits before replacing a working setup.

The founder notice on Texts.com is especially relevant for paying customers: it says current Texts subscriptions grant Beeper Plus features. Confirm that entitlement inside your Beeper account before canceling or buying a second subscription. If it does not appear, use the product support path with the email tied to the original subscription. A receipt and the original Texts sign-in are useful evidence; a claim about feature access on a public page is not proof that your particular account has been linked correctly.

Some familiar features now have different limits. Beeper lists account caps by tier: Free allows five total accounts and one per network; Plus allows ten total and three per network; Plus Plus removes those caps. The caps apply to connected accounts, not simply to the number of logos you see. A personal and a work WhatsApp number are two accounts. Check that distinction before you decide whether the Texts subscription benefit covers your actual setup.

No. The July 2025 Beeper launch explanation introduced connections where the app on your device contacts the messaging network directly. It also told existing Beeper Cloud users their connections would continue working during a gradual change. As of November 2026, the Beeper Plus FAQ still names Google Messages, Slack, Discord, LINE, and Google Chat as Cloud-only connections. It also says Beeper Cloud allows one account per network, even on a paid tier.

That distinction affects a real decision. Suppose you have two Telegram accounts and a Slack workspace. A Plus subscription can allow multiple Telegram accounts through on-device connections, while the documented Cloud constraint still limits the Slack network to one connected account. Paying for a higher tier does not turn a Cloud-only network into an on-device one. Look at the connection method for each account, especially if local message handling or multiple accounts is your reason to move.

Beeper explains its two architectures in terms of data flow: on-device messages go from your device to the network, while a Beeper Cloud connection uses Beeper servers between the client and network. Its FAQ says Cloud messages are stored encrypted. Ask which path a specific network uses and how recovery works before treating “Beeper is on-device” as a statement about every chat. For someone using both WhatsApp and Slack, the answer can differ inside the same Beeper installation.

Changing the app that displays your inbox can expose a history gap. Beeper’s history import guide says a newly connected network may import all, some, or none of its earlier messages. On-device connections start with the latest 50 messages in each chat and may load more as you scroll, within the network’s limits. The guide warns that removing and reconnecting a network can wipe its related messages and media from the Beeper account without guaranteeing a full reimport.

Use one old, important conversation as a test. Open it in the original network app, note an older phrase and attachment, then look for those in Beeper. Repeat after reconnecting only if support advises it and you know what may disappear. Keep the network’s own app and backup path available. A search result in Beeper is useful; it should not be your only copy of a legally or commercially important exchange.

The current Beeper iMessage guide describes a Mac-only connection that automates Apple’s Messages app. The iMessage chats live in Beeper Desktop on the Mac where the connection is made; they do not appear in Beeper on other devices. If you spend your day on Windows or Android, test that boundary before adding iMessage to your “all chats” plan. It is a specific Mac workflow, not a general route to iMessage across every Beeper device.

Beeper Mini is part of the history, but it is easy to mistake that episode for the fate of the whole company. In December 2023, Beeper reported an iMessage outage and a revised Mini release. In that same account, it reproduced Apple’s statement that Apple had blocked techniques using fake credentials to access iMessage. Beeper then said on December 21 that repeated disruption made the approach unsustainable. The current Mac-based iMessage method is materially different from the old Android Mini promise.

The lesson for a buyer is narrow and practical: distinguish a product’s current documented connection from an old headline about a different connection. Beeper’s Mac iMessage setup has specific permission and device requirements. Other networks have their own connection paths. A working Telegram account does not prove that an iMessage chat will show on an Android phone, and an old Beeper Mini news story does not mean Beeper itself closed. Test the exact network and device combination you need.

It changes one part, within a defined region and program. The European Commission’s Digital Markets Act explainer says designated messaging gatekeepers must provide basic interoperability to qualifying third-party messaging providers. It identifies WhatsApp and Messenger as Meta services under that obligation, with phased requirements for individual messages, groups, and later calls. The Commission says the first third-party services interoperable with WhatsApp launched in November 2025.

Meta’s European third-party chats announcement names BirdyChat and Haiket and describes an opt-in experience for eligible users in Europe. That is meaningful progress toward messaging between participating services. It does not say any consumer aggregator can import an entire personal WhatsApp inbox or that every messaging network has become open to one universal client. Beeper’s supported connections and their limits still need to be checked on Beeper’s own pages.

For example, if your use case is talking to a friend on an eligible third-party service from WhatsApp in Europe, the DMA rollout may matter. If your use case is searching ten years of WhatsApp and Telegram history in one desktop app, it does not establish that capability. Keep the regulatory change and the product feature you need as separate questions.

Start with an inventory of accounts, not an app deletion. Write down every connected network, the login email for Texts, which Texts subscription you pay for, and the devices where each conversation must appear. Then install the current Beeper app from its official download page. Sign in with the intended account, check whether Beeper Plus appears, and add one low-risk network first.

Compare a current message, an older message, an attachment, and a reply against the original service. Beeper’s desktop getting-started guide says backfill and available features vary by network. Check that the messages you would actually need can be retrieved, then try the next network. If you use two accounts on one service, verify the per-network tier limit and whether the service permits on-device connections.

Do not remove a working Texts app or cancel its subscription just because a new Beeper inbox opens successfully. Confirm the entitlement, then compare a week of real use: notification arrival, searching old messages, replying, and the device you use away from your desk. If something fails, you still have the original network app and enough detail to tell support exactly which account, network, and date is missing. The Texts founder notice recommends the new app but does not promise that every old local state transfers automatically.

The first mistake is equating a merger with a shutdown. Beeper is active and the Texts site still directs existing users; the useful question is which app now receives development and whether your account has the promised Plus entitlement. The second is assuming “on-device” covers every network. Beeper’s own plan guide still lists Cloud-only networks, so check each connection before making a privacy or multi-account decision.

The third is deleting a connection to fix missing history. Beeper warns that removal deletes messages and media from its account view and may not restore them on reconnection. Check the network’s original app and the documented backfill limit first. The fourth is choosing from a logo count: iMessage on a Mac, Slack through Cloud, and WhatsApp on a phone can have very different behavior even though all appear beside one another in an inbox.

If the job is a broad personal messaging inbox, Beeper’s network range is a strong fit. If you need conversations beside contacts, companies, deals, notes, and files, Pantheon offers that workspace for supported Telegram, WhatsApp, iMessage, and X DMs. X is a paid add-on and encrypted X Chat is excluded; Instagram DMs are not captured. iMessage needs a Mac, while WhatsApp needs the Mac app or a supported phone host in the private mobile alpha. Cross-channel identity matches are suggestions you approve. Try one real relationship and keep the original apps while you check it. See the unified inbox for current scope.