What a screen sharing session actually costs in battery and data
Screen sharing is one of the more demanding things a phone can do, because three expensive systems run continuously at the same time. The numbers are predictable, and so are the levers.
Where the battery goes
- Video encoding. Every frame of your screen is compressed in real time. Modern phones do this on a hardware encoder, which is far cheaper than software but not free.
- The radio. Sustained upload keeps the radio in a high-power state continuously. On mobile data this is typically the single largest draw, and it is worse with a weak signal, because a phone with poor reception transmits harder.
- The screen. Sharing usually means the display stays on, and on most phones the display is the biggest consumer of all.
- Heat, indirectly. Sustained encoding warms the phone, and a warm phone throttles — so a long session gets slower as well as shorter.
Rough expectation: a continuous sharing session drains meaningfully faster than video playback and slower than gaming. Fifteen to thirty per cent an hour is a realistic band on a mid-range phone, and the spread inside it is mostly about signal strength and screen brightness rather than the app.
Where the data goes
The stream is video, so consumption depends on how much the picture changes. Reading a static screen costs a fraction of scrolling through a feed or watching a video.
| What is on screen | Typical rate | Per hour |
|---|---|---|
| A mostly static screen — settings, a document | ~0.3–0.8 Mbps | ~150–350 MB |
| Normal use — scrolling, typing, switching apps | ~1–2 Mbps | ~450–900 MB |
| Constant motion — video, games, maps panning | ~2–4 Mbps | ~0.9–1.8 GB |
Two things people get wrong about this. It is the sharing phone that spends the upload, which is the constrained direction on almost every connection — so the phone showing its screen is the one that matters for both data cost and quality. And the receiving side spends download, which is usually plentiful and cheap.
Cutting both, in order of effect
- Be on Wi-Fi if you can. Removes the data cost entirely and reduces the radio draw substantially.
- Lower the resolution or quality if the app offers it. Halving resolution cuts the bits needed roughly fourfold, and a support session does not need a pixel-perfect stream.
- Turn the brightness down on the sharing phone. The viewer sees the captured framebuffer, not your backlight — brightness affects your battery and nothing else.
- Stop the session when you are talking rather than showing. Sessions left running through a conversation are the most common source of waste.
- Plug in for anything long. Simple, and it also removes the thermal throttling that makes a long session degrade.
- Close what else is uploading — photo backup in particular, which competes for exactly the constrained direction.
If the phone gets hot
Warmth is normal; too hot to hold is not. If it gets there, the phone is already throttling and the session quality is dropping as a result. Take the case off, stop charging while sharing if the phone is hot (charging and encoding together is the worst thermal combination), lower the resolution, and take breaks on long sessions.
And if a session drops after twenty minutes with no error, consider that the phone may have been stopped rather than disconnected — see why Android keeps killing the app.
More guides
Why the remote tap lands late, and which of the five causes is yours
Capture, encode, network, decode and the input path back each add delay. How to tell them apart from the symptom, and the fixes that actually change the number.
What happens when the shared phone locks or its screen goes off
Locking, the screen timing out and the phone being pocketed are three different events with three different outcomes. Why sessions die there, and what to change.
Picture but no control, freezing, or a black screen: a diagnosis order
Six symptoms that look alike and have completely different causes. What each one tells you, in the order that finds the answer fastest.
Try Remote Phone
Share an Android screen, or control one from another phone or your computer's browser. No account needed.
Try Remote Phone