Chrome Downloads

Available on Free and Pro, with no extra runtime. Files go through Chrome’s download system, normally beneath WebToSpark in the configured downloads location. Browser settings can affect prompts and the final destination. Check the completed download rather than assuming a path.

Authorized directory — Pro

Choose a local directory from Options using Chrome’s folder picker, grant write access and select that target for export. Browser restarts can require reauthorization. Reopen Options and grant permission under a click if saving stops. The real OS picker and retained permissions still require manual verification.

macOS Native Host — Pro

This optional local program requires macOS and Node.js 18 or newer. Ordinary Downloads and authorized-directory exports do not require Node.js. The host has no network access and writes beneath the root you configure.

  1. Use the Native Host installer with the unpacked extension ID shown in chrome://extensions.
  2. Reload the extension, then open Options → Native Host → Test connection.
  3. Set the output directory; writes are rejected until a root is configured.
  4. Make a small export and confirm the resulting file exists in that directory.

Limits and recovery

Native Host files have a maximum size of 32 MiB in this version. Larger exports need fewer sources or less included content. Host writes validate the transfer before committing a file. An uncertain write is not automatically retried: inspect the destination first.

A Free installation cannot use Pro directory targets; the background export logic falls back to Downloads.

Troubleshooting ↗Free and Pro ↗