How to Charge Your Phone With Another Phone
Running out of battery with no wall outlet in sight is a genuinely frustrating situation. The good news is that modern smartphones have made it possible to share power between devices — but how well that works depends heavily on the phones involved, how they're connected, and what you're trying to accomplish.
What Makes Phone-to-Phone Charging Possible
Most flagship and mid-range Android phones released in the last several years include a feature called reverse wireless charging (sometimes branded as PowerShare, Wireless PowerShare, or Reverse Charging). This lets a phone act as a wireless charging pad, broadcasting power outward through its back panel using the Qi wireless charging standard.
Additionally, many phones support USB Power Delivery (USB-PD) — a protocol that allows power to flow in both directions over a USB-C cable. This means one phone can technically supply power to another through a cable, provided both devices support the right negotiation protocols.
iPhones, as of recent generations, support MagSafe and standard Qi wireless receiving — but Apple has not enabled reverse wireless charging on iPhones. An iPhone can receive wireless power from another phone's pad, but it cannot broadcast power outward to charge another device wirelessly.
The Two Methods: Wireless vs. Wired
Reverse Wireless Charging
This is the most convenient method when available. You place the receiving phone face-up on the back of the broadcasting phone, align the coils, and charging begins automatically.
What affects performance:
- The broadcasting phone's reverse charging wattage (typically 3W–15W depending on the model)
- Case thickness on either device — thick cases block inductive transfer
- Coil alignment between the two phones
- The receiving phone's wireless charging capability
Reverse wireless charging is generally slow compared to wired methods. At 5W output, it's roughly equivalent to older-generation wireless chargers. It's best suited for topping off a device in an emergency rather than fully charging it.
USB-C to USB-C Cable Charging
This method uses a physical cable and can be faster than wireless — but it's not universally supported.
For phone-to-phone USB charging to work:
- Both phones need USB-C ports
- The supplying phone's firmware and hardware must support acting as a power source (OTG host mode with power output)
- The receiving phone must accept incoming USB power
Some Android phones explicitly support this and may even prompt you when a cable is connected asking whether you want to share power or transfer data. Others will only allow data transfer or won't recognize the connection at all.
⚡ Lightning-equipped iPhones cannot participate in cable-based phone-to-phone charging as either source or receiver through their Lightning port — USB-C to Lightning adapters don't enable power negotiation in this direction.
Key Variables That Determine Your Results
| Variable | Why It Matters |
|---|---|
| Broadcasting phone's battery capacity | Larger batteries (4,500mAh+) can share more without draining critically |
| Reverse charging wattage | Higher wattage = faster top-up for the receiving device |
| Receiving phone's wireless capability | Some older phones can't receive Qi at all |
| Cable quality | Poor-quality USB-C cables may not support PD negotiation |
| OS and firmware version | Manufacturers sometimes enable or restrict these features via updates |
| Phone cases | Thick or metal cases significantly reduce wireless charging efficiency |
What to Realistically Expect
Phone-to-phone charging is a bridge solution, not a primary charging method. Here's what the experience typically looks like in practice:
- Reverse wireless at 5W: Adds roughly 10–15% charge to a receiving phone over 30 minutes, while drawing down the host phone by 15–20% (accounting for conversion inefficiency)
- USB-C wired: Can be faster — some implementations push 10W or more — but speed depends on both phones' negotiated output and input limits
- Heat: Both phones will warm up during the transfer, which is normal but worth monitoring in hot environments
The host phone always loses more charge than the receiving phone gains due to the energy conversion process. This is an unavoidable consequence of wireless energy transfer inefficiency (Qi conversion typically runs at 60–80% efficiency) and the power management overhead of both devices.
Android vs. iOS: A Practical Difference 🔋
Android's ecosystem is where phone-to-phone charging is most broadly supported. Samsung Galaxy flagships, Google Pixel devices, and many Xiaomi, OPPO, and Huawei phones have supported reverse wireless charging for several generations.
Apple's approach keeps iPhones as receivers only in the wireless charging ecosystem. You can charge an iPhone from an Android phone's reverse charging pad — but not the other way around, and not via cable.
This asymmetry matters if you're in a mixed-device environment. An Android user can help an iPhone user in a pinch wirelessly, but an iPhone user cannot return the favor in kind.
The Setup Details That Often Get Overlooked
Even when both phones technically support the feature, small configuration details can prevent it from working:
- Battery Saver mode on many Android phones automatically disables reverse charging when active
- Some manufacturers require you to enable reverse charging manually in settings before it functions
- The host phone may automatically stop sharing power when its battery drops below a set threshold (commonly 20–30%)
- In USB-C wired scenarios, the direction of power flow is determined by the negotiation handshake — simply plugging in the cable doesn't guarantee which phone acts as the source
Whether phone-to-phone charging is a practical option for you comes down to the specific phones you're working with, how often you'd actually need to use the feature, and whether the charge speeds and battery trade-offs make sense for your situation.