Seamless trusted phone-browser onboarding is not ready. The current private-testing option uses a local certificate authority that must be explicitly trusted on the phone. If you do not want that setup, wait for a supported release. Never bypass a certificate warning.
1. Open the Windows preview
The Windows x64 executable bundles its runtime: you do not need a separate Node.js installation. The current build is unsigned. Review its status and checksum on the download page, and do not disable Windows security controls to run it.
2. Prepare a trusted phone connection
For private testing, ByteDrop Settings contains advanced local HTTPS setup. Transfer only the public certificate/profile through a trusted channel and follow your phone’s explicit trust process. This is a manual development flow, not the intended final onboarding experience.
Keep both devices on a network you control. Guest Wi-Fi or access-point isolation may prevent devices reaching each other. Changing a port does not establish identity or encrypt traffic.
3. Scan the fresh QR and approve
Scan the computer’s current QR. Check that the browser reports a trusted connection. Request access, then approve the request inside ByteDrop on Windows. Invitations expire and are single-use; after restart or revocation, request fresh approval.
4. Share originals and folders
Choose files or use a supported folder picker. Progress appears in compact notifications. Compatible directory pickers preserve empty directories; file-list compatibility pickers may omit them. Files appear only after verification and publication.
5. Recover safely
Pause before changing networks or closing the app when possible. Resume retained uploads after reapproval. On Windows, managed receiving rechecks the source and local chunks before continuing. Changed source content requires an explicit restart; old and new versions are never silently mixed.