Transfer files between Windows PCs on a private LAN with Blitzer
Pair two Windows PCs, choose a safe destination, verify a Blitzer file transfer and resume interrupted work on a private local network.
Check the network and Windows requirements
Blitzer requires Windows 11 x64 and two reachable devices on a private local network. Guest Wi-Fi and access-point isolation can prevent devices from communicating even when they share a network name. This version has no internet relay, public sharing link or AirDrop integration. Physical Mac-to-Windows interoperability remains unverified.
Discover and deliberately pair the peer
Open Blitzer on both computers and choose the discovered peer. If discovery is unavailable, use the other device’s private local IP address. Compare the six-digit codes shown on both computers before approving pairing. If an established peer’s identity changes, stop and verify the device instead of accepting it blindly. Handle any Windows permission choice yourself in line with your network policy.
Choose originals and a separate receiving folder
Start with a small, non-sensitive example containing the file types and folder names you use. Approve the offered transfer and receiving location on the destination PC. Blitzer stages received content and promotes it to a unique new folder after verification; it does not replace existing destination files. Keep the original until you have checked the complete result.
Review completion rather than only the progress bar
The transfer checks chunks with SHA-256 and verifies the staged result before reporting completion. Read the receipt, compare the expected files and open representative received files. Content checks establish byte agreement for the checked data; they do not establish the safety of an unknown file. Do not run a received executable just to verify a transfer.
Resume an interruption with the same paired peer
Keep the incomplete receiving stage and reconnect to the same peer to resume the last transfer. Verified chunks can be retained; corrupt staged chunks are removed for retransmission. A completed transfer creates a separate result folder, so review available destination space before retrying a large library. Do not treat a staged, incomplete directory as a completed backup.
Choose a backup workflow when that is the actual task
A local transfer helps move files between devices, but it does not by itself create a recurring, independent backup with version history. Keep a recoverable original and a separate backup of important data. Use the file-management guide to distinguish transfer, organisation, cloud placeholders and verified copying.