Account & threads
Sign in with the email/Google account you use on claude.ai and every existing thread, Project, and Artifact appears. Conversations sync in real time across the phone, tablet, and web.
A native Android app that signs into your existing claude.ai account, picks up where your web threads left off, and adds the things only a phone can do: voice conversations on a walk, the camera as a question, and the Android sharesheet as a bridge from any other app into a chat.
A complete guide for the Android side of the fleet — Pixels, Samsungs, OnePlus, foldables, Chromebooks running Android apps, Android tablets. Install, voice mode, camera, sharesheet workflow, the diversity-of-devices reality, plans & limits, recipes that pay off, what's harder than on the web, and troubleshooting.
Open claude.ai/download → routes to Google PlayUnderneath, this is the same Claude as claude.ai: same Opus, Sonnet, and Haiku, same Projects, same thread history, same usage limits on your existing plan. The app adds three doors the browser doesn't have: voice, the camera, and the system sharesheet. Everything else is the web experience packaged into something that fits in your pocket and runs offline-tolerant.
Sign in with the email/Google account you use on claude.ai and every existing thread, Project, and Artifact appears. Conversations sync in real time across the phone, tablet, and web.
No "mobile plan." Free, Pro, Max, Team — whichever you pay for on the web is what you get on Android. Usage on the phone draws from the same cap as the web.
The same picker — Sonnet as the daily, Opus when you want to think, Haiku when you want speed. No "lite model" sneaks in because you opened the phone.
Talk to Claude. Interrupt mid-sentence. Carry on while you walk, drive (as passenger), or cook. The microphone and speaker do the work; the model is the same one you'd talk to on a laptop.
The camera button in the composer takes you straight to a viewfinder. Point at a label, a plant, a menu, a broken thing. The friction to "ask Claude about what's in front of me" drops to two taps.
Every Android app's Share button now lists Claude as a destination. Articles, PDFs, screenshots, YouTube links, Drive docs, Maps locations — anywhere you can hit Share, you can hand to Claude.
Three Android conventions tip the balance for some workflows:
The Android app installs on Chromebooks with Play Store support and on Android tablets (Pixel Tablet, Galaxy Tab, Lenovo). Same APK, same features, more screen. The keyboard shortcut Ctrl+Enter sends a message; Ctrl+N opens a new chat on most tablet keyboards.
Voice mode is the single most under-appreciated feature of the app. Tap the voice button and you're in a conversation: speak, Claude listens, Claude replies, you can interrupt. The microphone and speaker handle the I/O; the model is the same one your web sessions hit. The reason this matters is that spoken Claude is a different product — looser, faster, paced for movement, willing to think alongside you instead of just answering.
The walk to lunch is twenty minutes of latent thinking time you weren't going to type out. Voice converts it: a problem to chew on, a plan to talk through, a draft you'd rather hear than write.
Spoken thinking is messier than written thinking — which is a feature when you're exploring. "Uh, so what I'm trying to figure out is — wait, no, the actual question is…" works in voice and would feel weird typed. Claude follows the drift; you don't need to compose first.
Voice is a smarter dictaphone — talk for two minutes, ask Claude to summarise back, iterate. Beats voice memos that sit forgotten in a list.
Cooking with your hands wet, walking the dog, driving as passenger, painting, gardening. Anywhere typing isn't an option, voice is.
Just start talking. The app uses voice-activity detection — when you speak, Claude stops. You don't have to wait for Claude to finish a paragraph. That's the unlock that makes the conversation feel real: you can redirect mid-sentence the way you would with a person, instead of waiting through a wrong answer before you can correct.
try_files directive" works typed; spoken, Gboard's speech-to-text often hears it as "try files directive" or "TryFiles direct" and Claude answers something slightly different."I'm about to walk and want to think through <X> — push back on me, don't agree too quickly" beats "what should I do about <X>." Claude treats the second like a request for an answer; the first like an invitation to a real exchange.
If you keep talking through Claude's reply, the app keeps treating you as the active speaker. A two-second pause lets the answer breathe and Claude get to depth — you'll get more out of it.
You don't need to start the conversation over. Voice mode handles "scratch that," "no, I meant the other one," "back to where I said X" cleanly. Treat the conversation like one with a person who's actually listening.
"Summarise what we decided" or "give me three bullet points to drop into my notes." That turns a 20-minute walk into a paragraph of actually-useful artefact.
Tap the camera icon in the composer. Frame the thing. Snap. The photo lands in the chat with your typed or spoken message. This is the surface that turns "I wish I could ask Claude about that" into a two-tap reflex. Use it for anything physical that doesn't translate to a typed description.
The back of a snack you've never bought. The ingredients list on a cosmetic. A wine label in a language you don't speak. Snap, ask "what is this, anything weird, anything I should know." Often more useful than a translation app because Claude has an opinion, not just a definition.
"What's this growing in the yard?" "Is this leaf turning the way a healthy hydrangea should?" "What bird made this nest?" Claude is honest about uncertainty — when it doesn't know, it says so, which is more than some specialist apps will do.
A kid stuck on a math problem. Photograph the problem, ask Claude to walk you through the thinking (not just give the answer), then check the kid's working. Useful for parents who haven't touched algebra since they last had to.
A breaker that won't reset. A check-engine light combination. A weird stain you're trying to identify before scrubbing it. Photograph, ask, work through the diagnostic with Claude.
A stuck error message on the kid's laptop across the room. The settings page of an unfamiliar smart-home device. Photograph, ask "what should I tap next."
End-of-meeting whiteboard photo → "transcribe this and clean it up into bullet notes." Sketch of an idea → "react to this like a colleague would." Better than re-typing the whole thing.
This is the workflow Android does as well as anything. Open the voice button. Tap the camera. Photograph the thing — your garage, your dashboard, your fridge contents — and then talk. Claude has both the image and the spoken context. The conversation becomes "so what you can see in this photo is the back left corner of the garage, and I'm trying to figure out where to put a workbench that doesn't block the breaker panel". That's not a query about a photo; that's a conversation about a place.
Android is more form-factor-diverse than iOS. The same APK runs on a compact 5.5" Pixel, a 6.7" Galaxy slab, a 7" inner-display foldable, an 11" tablet, and a Chromebook with a desktop-class keyboard. Claude resizes to all of them; some are markedly better than others for specific use cases.
The bread and butter. Large-screen phones (anything 6.5" and up) make the typing experience tolerable and the camera composer comfortable. Small-screen phones constrain typed work but voice mode is unaffected. The killer combo on a phone is voice + sharesheet — that's where the mobile app earns its place against the web.
The tablet is the sweet spot the iPad popularised — wide enough for real reading, light enough for the couch, close enough to a laptop to draft prose with two thumbs or a thumb-and-finger. With a Bluetooth keyboard it becomes a small laptop. The Claude app uses the extra width for a side panel of threads on the left, the chat on the right — much faster jumping between conversations than on a phone's drawer.
Where Android genuinely beats iOS for Claude. Open the foldable into a 7"+ inner display, run Claude on one side and Chrome (or Drive, or Gmail) on the other. Drag content from the other app into Claude. The two-pane workflow that iPad's Split View attempts is more fluid on a foldable because the OS treats the second pane as a real app, not a sidekick.
On Chrome OS and on Samsung's DeX mode, the Claude Android app runs in a resizable window like a desktop app. With a real keyboard Ctrl+N starts a new chat, Ctrl+Enter sends. For students or for anyone using a Chromebook as their main device, this is genuinely a viable "Claude on a laptop" experience without the laptop.
Every message you send syncs to your account in the cloud immediately. Open claude.ai on a laptop and the thread you just spoke into on your phone is right there — current, ready to continue. The mobile app isn't a separate Claude; it's a window into your existing one.
| Item | Android ↔ Web | Notes |
|---|---|---|
| Threads | ✓ live sync | Both directions, within seconds of connectivity. |
| Voice transcripts | ✓ as text | A voice session on Android appears as a typed thread on the web. Searchable. |
| Projects & uploaded files | ✓ synced | Add a file to a Project on the web; the same Project on Android sees it. Vice versa. |
| Artifacts | ✓ viewable | You can view rendered Artifacts on Android; editing them is friendlier on the web. |
| Custom instructions | ✓ synced | Set once on either surface, applied everywhere. |
| Camera photos in chat | ✓ shows on web | Photos you snapped on the phone appear inline in the same thread on the web. |
| App theme | ~ per device | Android follows your system theme by default; the web has its own setting. |
| Notifications | ~ per device | Per-channel Android notification settings stay on the phone. |
Capture on the phone (voice, camera, share). Refine on the web (when you've got a keyboard). Ship from wherever closes the loop. The reverse direction also works — finalise something on the laptop, then carry it on the phone for follow-ups during your day. Where it falls apart is when you try to do dense work on the phone: long writing, code, multi-Artifact iteration. Hand off, don't fight the form factor.
Inference happens in Anthropic's data centres, not on the device — the model is far too large to fit on any phone. That makes the app a thin client over the cloud. Treat it the way you'd treat the web app: anything you'd hesitate to paste into a browser, hesitate to paste into here too.
Claude app → Settings → Privacy → require fingerprint/face to open. Cheap insurance against shoulder-surfing if your phone gets unlocked but you don't want Claude immediately visible to anyone glancing at it.
Long-press a thread → Delete. It's removed from your account everywhere — phone, web, anyone you'd shared it with. If you want certainty, verify on the web at the same time.
Android Settings → Apps → Claude → Notifications → "Show on lock screen" → hide content. Toast title shows but message body stays hidden until the phone's unlocked.
Android Settings → Apps → Claude → Permissions → toggle Camera or Microphone off. The app still works without; you just lose those features. Re-enable any time.
Short version: there is no separate "mobile plan." Whatever you pay for on claude.ai applies here, with the same model availability, the same monthly cap, the same upgrade flow. Voice and camera aren't gated separately — if you have the app, you have them.
| Plan | Voice | Camera | Models | Cap |
|---|---|---|---|---|
| Free | ✓ | ✓ | Sonnet | Daily cap (varies); a "back later" notice appears when you hit it. |
| Pro | ✓ | ✓ | All models incl. Opus | Roughly 5× free, rolling 5-hour window. |
| Max | ✓ | ✓ | All models, priority on Opus | Roughly 5× or 20× Pro depending on tier. |
| Team / Enterprise | ✓ | ✓ | Plan-defined | Per-seat caps, pooled at workspace. |
Voice burns through the budget faster than text — a 10-minute voice conversation is more tokens than a 10-line typed exchange. Heavy voice users on the free tier will hit the cap regularly; Pro often pays for itself within a couple of weeks of daily voice use.
A banner above the composer shows remaining usage when you're getting close. When you hit the cap, the next send is blocked with a reset-time notice. Voice mode disables first; text continues on the smaller model for a while before the hard wall.
Each of these is a real use the phone is better at than the web — not because Claude is more powerful on Android, but because the situation only happens away from the desk.
Set a 20-minute walk. Before you leave: open Claude, tap voice, say "I'm going to walk and think through <X> out loud. Push back on me. Ask clarifying questions. Don't agree too easily. Summarise at the end." Walk. Talk. Pause when you need to. The transcript and the summary are waiting when you sit back down.
Snap the ingredients on something unfamiliar. "Plain English: what is this, what's it for, anything to avoid?" Faster than reading the label, much better than the brand's marketing copy.
Photograph the problem. "Don't give the answer. Walk me through how to think about it so I can explain to a fourth-grader." You get a one-paragraph teaching script; the kid gets a parent who suddenly looks like they remember.
On the way to a meeting you forgot to prep for. Share the calendar invite to Claude. "I'm walking into this in fifteen minutes. Three things I should remember, two questions worth asking, one thing I shouldn't commit to."
Tap a restaurant or landmark in Google Maps → Share → Claude. "What do I need to know about this place before I go. What do they do well, what to avoid, anything quirky about the etiquette." Reviews are noise; Claude's answer is signal.
On a long drive (as passenger). Voice on. "Let's plan the talk I'm giving on Friday. Argue against my main point so I can stress-test it." Two hours of road = two hours of structured thinking. (Don't do this driving solo, obviously.)
Photograph the broken thing. "What am I looking at, what's likely wrong, and what would the part be called if I were ordering one?" Now you have the vocabulary to actually search the parts store.
Restaurant. Menu in Vietnamese, Hungarian, Greek. Snap it. "Translate this and tell me which dishes I'd probably like if I usually order <X>." Translation apps stop at the words; Claude has an opinion.
Open the fridge. Photograph the contents. Voice on. "Dinner in thirty minutes. Walk me through one option using mostly what you see here. Veto anything needing a preheated oven."
You've pulled over. A long Gmail thread you've been avoiding. Share the whole thread to Claude. "What's the actual decision needed here, and who's blocking, and what's the one-sentence reply that closes it."
Voice, the camera, and the sharesheet are the wins. Some things are worse on a phone — knowing which is what keeps you from fighting the form factor when you could just open the laptop.
Anything past two paragraphs is uncomfortable on a phone. A tablet with a keyboard is workable; a foldable in book mode is workable. The web is still the right surface for drafting, editing, or anything where you'll iterate on wording.
Reading code on a phone is possible; reviewing it is painful. Code wants width — function signatures, indentation, side-by-side diff. Read summaries on the phone; do the actual review on the laptop.
Artifacts render fine; editing them (especially complex HTML or React) is much friendlier on the web. Use mobile to view and ask follow-ups; switch surfaces to actually change the code.
The Android sharesheet handles one file or one URL per tap. Multi-file uploads (drop a folder of PDFs into a chat) need the web's drag-and-drop. The Files app helps but is fiddlier than a desktop file picker.
On a phone the answer is "swipe back and forth." On a foldable, Split Screen works. On a tablet, it depends on the manufacturer's multi-window. The web is just two browser tabs.
Search exists on Android but the results UX is denser on the web. For "that thing I asked Claude about three months ago," start on the web.
If Claude isn't in the favourites row of every app's share menu, you'll use it 10× less. Long-press, Pin, done.
"Push back on me, don't agree too quickly" sets up a different conversation than "what should I do." Worth the extra sentence.
If you want more than a one-liner from voice, leave a beat of silence after your question. Otherwise the app keeps you in the speaker role.
"Summarise what we decided" turns a walk into a paragraph of notes. Otherwise you have a transcript you'll never read again.
The camera + voice combination is faster and richer than camera + typing. Worth the practice.
Snap, hit Markup, circle the relevant part, then share to Claude. The annotation does the work of a paragraph of "look at the bit in the upper right."
Projects (with their files and instructions) are available on Android. Start mobile chats inside the relevant Project so Claude already has context.
Switching to another app usually pauses or ends voice. If you need to look something up mid-conversation, ask Claude to look it up.
Voice for exploration. Type for precision, copy-ability, anything technical. Mixing them is the actual skill.
If you're a heavy typer on the phone, Gboard's swipe input is faster than tapping. SwiftKey is faster than Gboard for some people. Pick the one that doesn't slow you down.
The phone is great for capture; the foldable or tablet is great for reading what you captured. Try one week of doing your evening Claude reading on the bigger screen.
The banner is the meter. Voice drains it faster than text. If you bounce off it weekly, Pro pays for itself.
| Symptom | Likely fix |
|---|---|
| Voice won't start. | Android Settings → Apps → Claude → Permissions → enable Microphone. Then force-stop and reopen. Voice also needs connectivity — try briefly on Wi-Fi if cellular is patchy. |
| Camera button is greyed. | Permissions → enable Camera. If still denied (some launchers cache the prompt), uninstall and reinstall. |
| Claude isn't in the sharesheet. | Open the Claude app at least once and sign in — that's what registers the share target with Android. Then go back to the source app, hit Share, look in the chip row. Pin it once you find it. |
| Thread isn't syncing to the web. | Pull-to-refresh on the web. If still missing, check the phone's connection — messages composed offline queue locally until they upload. |
| "Couldn't process this image." | Usually the image is too small, too dark, or in an unusual format (HEIC sometimes misbehaves on older Android). Try a clearer shot or convert to JPEG first. |
| App is slow / laggy. | Force-stop (Settings → Apps → Claude → Force stop) and reopen. If it persists, clear cache (same screen, Storage → Clear cache — this is safe, leaves you signed in). If still bad, uninstall and reinstall; threads are in the cloud, nothing is lost. |
| Voice cuts me off mid-sentence. | The voice-activity detector thinks you're done. Try fewer micro-pauses. If the version exposes Push-to-Talk (a held-mic icon), use that instead — your turn ends when you let go. |
| Notifications don't fire. | Android battery optimisation often kills background apps. Settings → Apps → Claude → Battery → Unrestricted. Some manufacturer skins (Samsung, Xiaomi) have an extra "auto-launch" toggle on top of that. |
| Photos from Photos come in blurry. | Google Photos sometimes shares a downsized version. From Photos, tap the photo, hit the three-dot menu, choose Original before sharing. |
| App reverts to light theme. | Android system theme override. Settings → Display → Dark theme. Or in the Claude app: Settings → Theme → pin to Dark. |
The Android app is one of six doorways into Claude. The other five complement it.