Gopeed
Gopeed 1.9.3 is an open-source cross-platform downloader built with Go and Flutter. It supports HTTP, BitTorrent, magnet links and ED2K, plus task management, browser extensions, command-line use, web mode and API or extension customization.
Tasks and supported protocols
Gopeed manages HTTP, BitTorrent, magnet and ED2K tasks across desktop, mobile, web and QNAP environments. Browser extensions, command-line access, Web mode and APIs make automation possible, but they also turn a downloader into a service that can read files, access networks and control tasks. Keep these interfaces within a deliberate trust boundary.
Version and platform differences
Version 1.9.3 adds ED2K support and fixes a case where an HTTP task without range support could write more bytes than the file size. Assets cover Windows, macOS, Linux, Android, iOS, QNAP and web builds, but background behavior, file permissions, signing and auto-start rules differ by platform.
Extensions and remote deployment
Gopeed's backend and Flutter frontend communicate through local HTTP or a socket, while web and API deployments add listeners, credentials, reverse proxies, container volumes and logs. Install only extensions whose code, update source and requested permissions can be reviewed, and never expose an unauthenticated task API to the public network.
Review date: 2026-08-06.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Gopeed to this cloud drive
Baidu Netdisk
Save Gopeed to this cloud drive
Gopeed 1.9.3 installation, protocol tasks and Web/API security guide
Install the build for the target platform, validate a small public HTTP file, then test BitTorrent and ED2K. Enable browser, web and API features last, with restricted listeners, tokens and extension permissions.
Before you start
- Match Windows, macOS, Linux, Android, iOS or QNAP with the CPU architecture, and back up old tasks, configuration, extensions and unfinished files.
- Separate temporary and completed directories, plan the service user and read-only mappings for web mode, and reserve enough disk space.
- Process only HTTP, BitTorrent, magnet or ED2K material you are entitled to access, and keep cookies, API tokens and private links out of public configuration.
Installation steps
- 01
Choose the 1.9.3 asset
Select Windows x64 or ARM64, a universal or architecture-specific macOS image, Linux AppImage, DEB or RPM, an Android ABI package or a compliant iOS installation path.
- 02
Set directories and conservative defaults
Separate temporary and completed files, start with conservative connections and concurrency, confirm HTTP size, BitTorrent file lists and ED2K paths, and do not auto-start every file in an unknown task.
- 03
Enable browser or web mode only when needed
Limit the browser extension to a test site, bind web or QNAP mode to a controlled interface, configure credentials and firewall rules, and keep the task API off the public Internet.
Quick start
- 01
Verify an HTTP file
Add a small public file, pause and resume it, and compare its size or checksum. Version 1.9.3 addresses non-range over-writing, but proxies, expired links and old tasks still need checking.
- 02
Review BitTorrent and ED2K scope
Inspect file list, save directory, upload behavior and disk usage before starting, select only required files and avoid sharing sensitive directories.
- 03
Connect extensions and API last
Install one extension at a time, test its domains and file permissions, use an independent least-privilege API token and revoke tokens or automation scripts when no longer needed.
Usage tips
- Version 1.9.3 adds ED2K and fixes the size anomaly for HTTP tasks without range responses; the project uses GPL-3.0 and remains actively maintained.
- Similar interfaces across desktop, mobile, web and QNAP do not guarantee identical file access, notification, background or auto-start behavior.
- Extensions are executable logic. Review their requests, update source and credential handling before adding a third-party protocol parser.
- Remote web deployment requires authentication, a reverse proxy and protected access logs; binding locally does not replace least-privilege volumes and service users.
Troubleshooting and uninstall
Why is an HTTP task stuck, unable to resume or larger than expected?
Confirm version 1.9.3, refresh the link, reduce concurrency and check server range support, proxy behavior and disk space. Remove a corrupted temporary result rather than renaming it into a completed file.
Why cannot the browser extension, web page or API connect?
Check the process, listener, port, token, firewall and reverse-proxy path locally first. The extension also needs its native bridge and site permission; opening public access or removing authentication hides the real issue.
- Export tasks and revoke automationStop downloads and seeding, export required tasks, remove API tokens, browser extensions, third-party scripts and remote clients, and close web or QNAP ports.
- Remove the app and runtime dataUninstall the app or remove the portable package, container or QPKG, decide which configuration, database, temporary and completed files should remain, and clear auto-start entries and service permissions.
Frequently asked questions
What changed in Gopeed 1.9.3?
Released on 2026-03-18, it adds ED2K support and fixes a case where an HTTP task without range support could download beyond the total file size. Existing tasks should still be checked for final size and integrity.
Can any Gopeed extension or API script be installed?
Extensions and APIs broaden network, file and task-control permissions. Review code, maintenance status and requested scope, keep web and API access authenticated and keep tokens out of scripts and logs.
Are iOS, web and QNAP packages identical to desktop builds?
No. Platform permissions, installation, signing, storage mapping and background rules differ. Validate the specific target platform instead of inferring feature parity from the version number.