Saved device profiles
Keep separate profiles for PCs, servers, NAS units, and lab machines with names, groups, device types, notes, and favorite status.
Local Wake-on-LAN for your phone
Wake PCs, servers, and NAS devices from iPhone or Android with clear profiles, explicit wake actions, and no cloud account in the path.
Built for the real Wake-on-LAN workflow
PacketWake focuses on the details that usually make Wake-on-LAN frustrating: MAC addresses, broadcast targets, ports, SecureOn, retries, and network boundaries.
Keep separate profiles for PCs, servers, NAS units, and lab machines with names, groups, device types, notes, and favorite status.
Wake is a deliberate per-device or per-group action. PacketWake does not quietly scan your LAN or pretend a sleeping device is online.
Use the default UDP port 9, change ports, add a broadcast override, set a SecureOn password, or send a small bounded retry sequence.
See recent wake attempts and failures so you know what the app tried, without turning that into misleading online/offline status.
How it works
PacketWake sends a magic packet that contains the target device MAC address. The target still needs firmware, operating system, adapter, and network support for Wake-on-LAN.
Guides
Privacy-first utility
Profiles stay in local app storage unless you explicitly export them. PacketWake sends Wake-on-LAN packets to the network target you choose.
FAQ
Not reliably without additional network checks. PacketWake records wake attempts and avoids presenting a sleeping or blocked device as confirmed online or offline.
The phone can usually be on Wi-Fi, but the target device often needs wired Ethernet and adapter support for waking from sleep or shutdown.
UDP port 9 is the common default. Some networks or tools use port 7. Match the target network and router configuration.