DuckCarryStart on a private network
Connect phone and computer to the same trusted private network. In DuckCarry choose Wi-Fi transfer, then Receive from phone. Open the displayed HTTPS address on the phone. Do not set up router port forwarding or install a root certificate/profile. The firewall may request private-network access. A receiver session lasts up to one hour; start again if it expires.
Verify before sharing the code
The temporary self-signed certificate causes a browser warning. In the browser's certificate details compare the entire SHA-256 fingerprint with the computer before entering the pairing code. If the browser cannot show those details, use the cable instead. Without this comparison you have not authenticated the receiver against an impostor on the network. Keep the code private.
Choose files and keep the page open
Use the phone's own file picker. Keep the browser visible while sending; this is not background library synchronization. The picker may provide a converted version rather than the library original. Files are sent one at a time with checked chunks; the per-file limit is 64 GiB. Completed files are kept in the computer's application inbox, which needs additional disk space.
Copy the inbox to your folders
Finish sending, return to the desktop and choose Copy. The inbox then follows the normal scan, allowance, destination/backup and verification flow. Receiving is not yet your final destination copy. Completed inbox files remain local for your management; incomplete files are not counted as successful copies. Phone files are not changed or deleted through a Wi-Fi source. Physical browser/network acceptance remains separate from automated tests.