Sending files works more widely than choosing a save folder
Current major browsers support the direct file connection and normal file selection. Folder selection is available in many current browsers, but support and file-provider behavior vary by browser, operating system, and device.
Choosing an exact save folder is a separate feature. Chrome and Edge can offer it on supported desktop systems. Firefox, Safari, and many mobile browsers save through the normal Downloads flow instead.
- WebRTC file transfer: available in current major browsers
- File selection: broadly available; folder selection varies by browser and platform
- Writable destination folder: limited to browsers and platforms that expose the picker
- Browser Downloads: requires enough temporary browser storage
Why large downloads need temporary browser storage
Before starting a normal browser download, AllFileGo keeps the incoming file in private temporary storage. This prevents an incomplete file from appearing as finished, but the browser needs enough temporary space for the full file.
If the browser lets you choose a destination folder, AllFileGo can place files there and preserve the folder structure without creating a ZIP file. The file is still verified before completion.
Why transfers may pause in the background
A browser may slow or suspend a hidden page to save memory and battery. Phones and tablets do this more often. Keep AllFileGo visible during a transfer when possible.
A normal download can continue after the browser's download manager takes control. An AllFileGo transfer still needs the page, its connection, and its temporary storage until verification finishes.
Choose the best receiving browser
Use a current browser on both devices. For a large folder on desktop, Chrome or Edge is usually the easiest receiver because it may let you choose a destination folder. In Firefox or Safari, use the normal Downloads flow and make sure enough temporary browser storage is available.