iPhone exports get most of the attention, but a large share of the phones that arrive at a family-law or civil office run Android. Android is not one system: the messaging app, the manufacturer, the carrier and whether a chat used SMS, MMS or RCS all change what an export captures. A careful export takes an hour; fixing a careless one can take a supplemental production.

This guide covers the Android collection step: what to check before exporting, the main export routes and their gaps, how to verify the file and how to document it. App names, menus and capabilities change between versions, so treat the specifics below as a checklist to confirm on the phone in front of you. For Apple devices, see our guide to exporting iMessages for litigation.

What should you check before exporting Android messages?

Five questions decide the route. Ask them with the phone in hand:

  • Which messaging app is the default? Many phones use Google Messages; some Samsung phones use Samsung Messages; others use a carrier or manufacturer app. Settings, then Apps, then Default apps shows it.
  • Do the relevant chats use RCS? RCS chats (often labeled “chat” or “RCS message” in the compose bar) behave differently from SMS and MMS in exports.
  • How far back do the messages go on the phone? Scroll to the start of each key thread. Message-limit settings or a phone upgrade may have cut the history.
  • Is there a second number or app? Dual SIM phones, work profiles, WhatsApp, Signal and Telegram all keep their own messages outside the default app.
  • Is there enough free storage? Backups with attachments can be large, and a backup that fails partway through may still produce a file that looks complete.

What are the options for exporting Android text messages?

RouteWhat it capturesGaps to check
Backup app writing an XML file (for example, SMS Backup & Restore)SMS and MMS with phone numbers, timestamps, thread grouping and attachments if MMS is includedRCS chats may be missing; MMS must be switched on; a date filter in settings can cut history
Manufacturer backup to a computer (for example, Samsung Smart Switch)Messages preserved for restoring to a phoneBuilt for restoring, not reading; often needs another tool to review
Cloud device backup (Google account backup)Messages restored to a new Android phoneGenerally not a downloadable, reviewable export
Forensic extraction by an examinerThe messaging databases the apps use, including RCS in many cases, plus deleted data on some devicesCost, time and device support vary by model and operating system version
Screenshots or screen recordingWhat was on screenNo years in many views, no identifiers, no attachments at full size

For most matters where authenticity is not seriously disputed, a documented backup export is the practical route, with screenshots kept for display only. When deletion is alleged, RCS chats are central, or the device is damaged, an examiner is usually the better tool. Our article on screen recordings of text messages covers when a recording is the only option.

How do you run an XML backup export correctly?

Most of the problems with Android exports are settings. Walk through them with the client, or have the client follow written steps while you watch on a video call.

  1. Choose what to back up. Select messages, and call logs if they are requested. Our guide to producing call logs and voicemail covers the call side.
  2. Include MMS. Group texts, photos, videos and long messages travel as MMS. Without it, group threads and attachments disappear.
  3. Remove date limits. Back up all conversations rather than a recent window, then filter to scope later in review, where the filter is documented.
  4. Turn on a human-readable date field if offered. It helps reviewers, but keep the raw timestamp too; that is the field your log should rely on.
  5. Save to a location you control. Write the file to the phone and transfer it by cable, or upload to a cloud folder the office provides. Avoid emailing large backups, which may be blocked or truncated.
  6. Record the run. Note the phone model, phone number, app and version, settings chosen, date and time, who ran it and the file name and size.

Template: client instructions for an Android export

Please keep your phone as it is: do not delete messages, reset the phone or switch phones until we confirm we have a complete copy. On [date] we will walk through the export with you on a call. Before the call, install [backup app] and make sure your phone has at least [amount] of free space and is charging. During the call we will select messages [and call logs], include MMS, choose all conversations, and save the file to [location]. After the export, please do not open, rename or edit the file. We will confirm receipt and record its details.

How do you verify an Android export before relying on it?

Check the file against the phone the same day, while the client still has the device handy:

  • The message count for two or three key threads matches what the phone shows, or the difference is explained
  • The first and last message dates in each key thread match the phone
  • Group threads list every participant and include messages from each of them
  • Photos and videos referenced in messages are present as attachments
  • Threads that used RCS appear in full, or their absence is recorded
  • Timestamps convert correctly; raw Android message times are typically stored in milliseconds from 1970 in UTC

Then hash the file and store the original untouched. The hash values guide covers how, and the chain of custody guide covers the log that travels with it. Time zone and daylight saving conversions are a frequent source of disputes; our guide to text message timestamps as evidence explains how to normalize and state them.

What Android-specific issues trip up reviews?

A few patterns come up repeatedly:

  • SMS and RCS in one conversation. A thread can switch between RCS and SMS when data drops or a participant changes phones. An export that captures only one channel shows a conversation with holes in it.
  • Reactions as text. When reactions cross between Android and iPhone, some arrive as separate text messages describing the reaction rather than as a reaction. Our article on emojis as evidence covers how to present them.
  • Emoji rendering. The same emoji can look different on Android and iPhone. Exhibits should show what the recipient saw, or note the difference.
  • Duplicate copies. A client who exported twice, or who also sent screenshots, creates duplicates. See deduplication and threading.
  • Other apps. WhatsApp and similar apps need their own exports; see WhatsApp evidence in litigation.

Once verified, the XML file is the source for review and production. Message Extractor auto-detects SMS Backup & Restore XML alongside iMazing, WhatsApp, Facebook, Instagram and Google Voice exports, merges duplicates into one thread model and renders a paginated, Bates-stamped log with an attachment appendix and a source manifest. If you only need one log for one matter, there is a per-matter option.

Turn an Android export into a numbered logOne-time $39 · no subscription

What goes wrong in Android message exports?

MistakeConsequenceFix
MMS left offGroup threads and photos missingInclude MMS; verify attachments
Recent-only date windowEarly messages missing from productionBack up everything; filter in review
RCS chats assumed presentHoles in key conversationsCheck RCS threads against the phone; escalate to an examiner
Phone replaced before verificationNo way to re-collectHold the device until the export is checked
No collection recordAuthentication questions at the hearingLog the device, app, settings, date and operator

Whether to retain a forensic examiner, how to describe gaps in a written response and how to handle a dispute over deleted messages are decisions for the supervising attorney. Courts differ in how they treat client-run exports, so confirm local practice with counsel licensed where the matter is pending, and see producing text messages in discovery for the steps that follow collection.