Google Messages Tests Bulk Forwarding: What the Beta Reveals
Google Messages may finally be fixing one of its most complained-about limitations. Researchers at Android Authority today enabled a bulk forwarding feature inside the latest beta build, walking through the complete flow end to end: select multiple texts and images, tap a new overflow menu, preview the batch, send. The feature is not publicly available, is described as a work in progress, and carries no release timeline.
The gap it addresses is hard to miss once you've run into it. Select multiple images in a Google Messages conversation right now and the app offers exactly two choices: delete or download. No forward option exists. Text messages are worse in a different way the three-dot menu that contains the Forward option disappears the moment a second message is selected, forcing users to repeat the entire sequence for each item individually, as Android Police documented earlier this year. The beta feature would collapse all of that into a single operation.
How the Google Messages forward multiple messages feature works in beta
Android Authority enabled the feature inside build messages.android_20260618_05_RC02.phone.openbeta_dynamic. With it active, selecting a mix of messages and images surfaces a three-dot overflow icon in the top-right corner of the conversation header an element that doesn't exist in the current stable version. Tapping it reveals a Forward option. From there, a contact picker opens, and a preview of the selected content appears at the bottom of the screen before anything is sent.
That preview is new, and not just for bulk forwarding. The current single-message forwarding flow has no such step you pick a recipient and the message goes. The beta adds a confirmation layer to both scenarios, giving users a chance to review what they're about to send. It's a small detail that signals the implementation has been thought through, not just bolted onto the existing UI.
Google is also testing a refreshed interface in the same beta build alongside these forwarding changes, according to Android Authority. Whether the interface work is a prerequisite for the forwarding feature or simply a parallel effort isn't clear from the reporting.
What the beta doesn't yet show
The mechanics handle the obvious problem. But the reporting leaves several questions open that will determine how useful the feature actually is in practice.
Whether the preview displays sender names, original timestamps, and message order is not addressed anywhere in the beta findings. Those details matter considerably. When forwarding a thread to someone who wasn't part of the original conversation, context is the whole point. A recipient needs to know who said what and in what sequence without that, a batch of forwarded messages becomes a content dump with no readable structure. Whether the final implementation preserves that context, across SMS, MMS, and RCS, is the question that separates a genuinely useful tool from a mechanical shortcut.
None of that is answered in the current beta, and it may not be until the feature is closer to a stable release.
What beta teardown evidence does and does not confirm
Android Authority is direct about the limits of this kind of finding. APK teardowns surface work in progress from unreleased builds, and features found this way may not reach a public release. This discovery sits a step beyond a typical code string: researchers enabled the feature and ran it through the full forwarding flow, not just found menu labels in disassembled code. That's meaningful. It still isn't a product announcement. Google hasn't acknowledged the work, and no ship date has been offered.
The distinction matters because Google has a track record of testing features in beta that never reach stable users. Beta evidence confirms development is underway. It doesn't confirm delivery.
Bulk forwarding fits a stretch of interaction fixes Google has moved on this year
Earlier this year, Android Police published a roundup cataloguing long-requested Google Messages features the company had left unaddressed. Bulk forwarding made the list. At the time, the report noted there had been no evidence Google was actively working on it. About five months later, a working demo exists in beta.
Two other small interaction fixes moved through beta during the same stretch. In January, a redesigned context menu began rolling out, relocating actions like Reply, Forward, Copy, and Delete from the top of the screen to a compact panel that appears directly below the selected message, Android Authority reported. An Android Authority contributor spotted it in the latest beta and posted about it on Reddit; several other beta users quickly confirmed they were seeing the same interface. The change makes one-handed use more practical on larger phones, where reaching the top of the screen for basic actions was an ergonomic problem.
Four weeks later, a different fix surfaced in beta. Android Authority reported in February that Google Messages was working on partial text selection: the ability to drag and highlight only a portion of a message before copying, rather than capturing the full text. Long-pressing a message in the current stable version copies the entire thing. For pulling a one-time password or a street address out of a longer message, that's an unnecessary friction. The updated context menu the same one introduced in January makes the message text selectable, with Android's system-level selection menu appearing once a portion is highlighted.
Bulk forwarding builds on that same context menu infrastructure. All three changes address persistent interaction problems that accumulated quietly over years of complaints.
Other long-standing requests from the Android Police roundup remain unaddressed as of this week: a trash folder for accidentally deleted messages, visual separation for pinned chats, and in-app payment support, among others. The progress on forwarding, context menus, and text selection doesn't signal a broader course correction just continued work on specific friction points.
What needs to be answered before this ships
The beta test shows Google has moved from a known gap to a working demo. That's further along than anyone could say in January. What happens next depends on details the beta doesn't surface.
Whether the final implementation carries sender attribution, message order, and timestamps across message types is what separates a usable forwarding tool from a stripped-down convenience feature. A forwarded exchange only makes sense to the recipient if they can follow who said what. Without that context, the feature solves the mechanical inconvenience the repetitive tapping while leaving the informational problem intact.
No timeline has been offered, per Android Authority. The feature may ship with full context preservation, it may ship without it, or it may not ship at all. What's clear is that Google is building it. Everything else is still open.
Comments
Be the first, drop a comment!