Access Your Local Dev Server From Any Device
Network setup, binding, and HTTPS tips for reaching your local dev server from phones, tablets, and other machines on your network.
6 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.
Bind to the right interface
By default many dev servers listen only on 127.0.0.1, which is unreachable from other devices. Binding to 0.0.0.0 makes the server listen on all network interfaces so other devices on your LAN can connect. This single setting fixes the majority of 'can't reach my dev server' problems.
127.0.0.1 is local-only and unreachable from other devices
0.0.0.0 listens on all interfaces
Vite: use --host; Next.js: -H 0.0.0.0
Confirm the chosen port isn't blocked by a firewall
Find your address and connect
Once bound correctly, find your machine's LAN IP and visit it with the port from any device on the same network. For features that need a secure context - service workers, camera, geolocation - you'll need HTTPS, which a tunneling tool can provide, or a locally trusted certificate via a tool like mkcert.
Get your LAN IP (ipconfig / ifconfig / system settings)
Visit http://your-ip:port from the other device
Use HTTPS for secure-context-only features
mkcert or a tunnel provides trusted local HTTPS
Keep every device in view
Reaching the dev server is half the battle; keeping all those devices visible and in sync is the other half. Sizzy gathers phone, tablet, and desktop viewports into one window pointed at your dev server, so once your binding and network are right, every device stays connected, hot-reloads together, and responds to synchronized input.
Point all viewports at the same dev-server origin
Keep them in one window for synced interaction
Benefit from shared hot reload across devices
Use a QR shortcut to add a real phone to the mix
Release checklist
Dev server binds to 0.0.0.0 (or --host).
The port is reachable through the firewall.
HTTPS is configured for secure-context features.
All devices share the same dev-server origin.
Frequently asked questions
How do I make my dev server accessible on my network?
Bind it to 0.0.0.0 instead of 127.0.0.1 - use --host with Vite or -H 0.0.0.0 with Next.js - then visit your machine's LAN IP and port from other devices on the same network, with the firewall allowing the port.
Why do I need HTTPS for local testing?
Features like service workers, camera, microphone, and geolocation require a secure context. Use a tunneling tool that provides HTTPS or generate a locally trusted certificate with mkcert so these features work on other devices.
What's the difference between 127.0.0.1 and 0.0.0.0?
127.0.0.1 is the loopback address reachable only from the same machine, while 0.0.0.0 tells the server to listen on all network interfaces so other devices on the network can connect.
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.