How to Test a Website on an Android Phone
How to open your site on a real Android phone, use remote debugging over USB, and cover Android's wide range of viewport widths.
7 min read - Updated 2026-06-15
Use this guide as a compact release reference, then validate the same breakpoints in Sizzy with synchronized devices and screenshot evidence.
Get your site onto the phone fast
There are three reliable ways to load your local site on an Android phone: put the phone on the same Wi-Fi and visit your machine's local IP, expose localhost through a tunneling tool, or use a QR-to-phone shortcut that opens the URL by scanning a code. The QR approach is fastest because it skips typing IP addresses on a tiny keyboard.
Same Wi-Fi: visit http://your-machine-ip:port
Tunnel localhost for phones on other networks
Scan a QR code to open the URL instantly
Ensure your dev server binds to 0.0.0.0, not just localhost
Use Chrome remote debugging over USB
For real inspection, enable USB debugging on the phone and open chrome://inspect on your computer. You get full DevTools for the page running on the actual device - inspect elements, read the real console, and profile performance on real hardware. This is the gold standard for diagnosing Android-only issues.
Enable Developer Options and USB debugging on Android
Open chrome://inspect on desktop Chrome
Inspect the live page with full DevTools
Profile real device performance, not emulated
Cover Android's width spread first
Android spans far more widths than iOS, so emulating the common classes locally before grabbing hardware saves time. Sizzy shows common Android widths side by side with synced interaction and a QR shortcut to jump to a real device, so you clear layout bugs in emulation and reserve the physical phone for performance and final checks.
Emulate 360px, 393px, and 412px before using hardware
Check larger 480px foldable and tablet handoff widths
Use QR-to-phone to reach the real device instantly
Reserve real hardware for performance and final QA
Release checklist
Dev server binds to 0.0.0.0 so the phone can reach it.
Common Android widths are cleared in emulation first.
chrome://inspect is used for real on-device debugging.
A real device confirms performance before release.
Frequently asked questions
How do I open my localhost on an Android phone?
Put the phone on the same Wi-Fi and visit your computer's local IP with the port, make sure your dev server binds to 0.0.0.0, or use a QR-to-phone shortcut to open the URL by scanning a code.
How do I debug a website on a real Android device?
Enable USB debugging on the phone, connect it, and open chrome://inspect in desktop Chrome. You get full DevTools for the live page on the device, including console, element inspection, and performance profiling.
What Android screen widths should I test?
Cover 360px, 393px, and 412px for common phones, plus around 480px for foldables and small-tablet handoff. Android varies more than iOS, so test a representative width per class rather than one flagship.
Related guides
Benji
Your life OS
The companion app that keeps every area of your world in sync.
Zero to Shipped
Ship products, not side projects
The ultimate Next.js boilerplate for building and launching real products.
DMX
Mindful Twitter/X
The intentional X client for macOS. Reclaim your attention span.
Sotto
Voice-to-text for macOS
Speak naturally. Type instantly. 100% local & private.
Passlock
Password manager with willpower
Lock passwords with time delays, word challenges, or hand the keys to someone you trust.
Glink
Changelogs that slap
Beautiful changelogs and roadmaps for your product.
JoinRepo
GitHub access control
Monetize your GitHub repositories with ease.
Tubely
YouTube Studio for Mac
Manage multiple YouTube channels in one native app.
JustWrite
Distraction-free writing
A minimal writing app that helps you focus on what matters.