FI
SOFTWARE

FileCentipede

A multi-protocol download and file-transfer tool for Windows and Linux x64, supporting HTTP(S), FTP(S), SFTP, WebDAV, BitTorrent, magnet links, m3u8 tasks, queues, rate limits and browser extensions.

Version 2.82Windows x64Linux x64Proprietary software; only selected demonstration source is public

What FileCentipede does

FileCentipede combines ordinary downloads, BitTorrent tasks, browser handoff and FTP, SFTP or WebDAV file management. Queues, rate limits and protocol-specific settings make it useful for multi-source workflows, but the program also handles credentials, browser cookies and remote file operations, so its permissions are broader than those of a simple HTTP downloader.

Version and authorization boundaries

The 2.82 release provides Windows x64 and Linux x64 portable assets plus Chrome and Firefox extension packages. A visible project repository does not automatically make the finished application open source; the product license, dependencies and download rights should be checked separately. Browser capture must stay within the user's access and download rights.

Maintenance note

This page reviews FileCentipede 2.82, supported platforms, multi-protocol tasks, browser extension scope, remote credentials, public DHT metadata and the distinction between demonstration code and the finished product. Content review date: 2026-08-23.

SAVE TO CLOUD

Save to your cloud drive

Open the cloud drive to get the file directly, or save it for convenient access on another device.

Links checked 2026-08-06
Save first, access when you need itOn desktop, scan with the matching cloud-drive app. On mobile, tap the save button.
GUIDE

FileCentipede 2.82 installation and multi-protocol task guide

Install the x64 build, verify a small public HTTP file, and enable browser capture, SFTP, WebDAV or BitTorrent only after the local download path is understood.

Before you start

  • Confirm Windows x64 or Linux x64 and reserve separate download, temporary and completed-file directories.
  • Prepare test files and low-privilege temporary accounts; clear browser cookies or headers that should not be handed to the downloader.
  • Only process files, streams and torrents that the account is entitled to access and save.
01

Installation steps

  1. 01

    Install the matching x64 build

    Extract the Windows or Linux 2.82 ZIP into a fixed directory and verify that the browser extension package is not being used as the main program.

  2. 02

    Set directories and concurrency

    Separate temporary and completed files, begin with low concurrency and confirm disk space, filename rules and proxy settings before increasing connections.

  3. 03

    Add a browser extension only when needed

    Choose the Chrome or Firefox package that matches the browser, review its site permissions and verify that it connects to the intended local application.

02

Quick start

  1. 01

    Verify a normal HTTP task

    Add a small public file, pause and resume it, then compare the final size and a trusted checksum. A server without range support cannot be forced to resume safely.

  2. 02

    Test protocols separately

    Test FTP, SFTP, WebDAV and BitTorrent one at a time with temporary low-privilege accounts, keeping passwords, private keys and cookies out of logs and exports.

  3. 03

    Restrict remote and browser access

    Bind remote features to a controlled address, add authentication and firewall limits, and remove cookies, headers and expiring URLs after a browser task ends.

Usage tips

  • A downloader cannot compensate for server bandwidth, access controls or a missing range request; more segments can trigger throttling.
  • Public BitTorrent discovery exposes peer metadata, so disable seeding and discovery features that the task does not need.
  • SFTP, FTP and WebDAV credentials should use the smallest directory scope possible and should be rotated after temporary use.
Troubleshooting and uninstall

Why is a completed file the wrong size?

Confirm the version, remote size, link validity and proxy stability, then lower concurrency and remove corrupted temporary segments before retrying.

Why did the extension capture the wrong cookie or fail to send a task?

Check the extension version, browser manifest, native connection and site permissions, then test in a normal window with a non-sensitive public file.

  1. Stop tasks and revoke accessStop downloads, uploads and seeding, export only necessary tasks, remove remote credentials and browser permissions, and confirm no service port remains open.
  2. Remove the program and extensionsDelete the Windows or Linux program and Chrome or Firefox extension, then decide separately whether completed files, task databases and temporary segments should remain.
FAQ

Frequently asked questions

Is FileCentipede fully open source?

No. Public demonstration code and dependencies do not establish an open-source license for the finished product. Check the product terms and each downloaded component separately.

Does FileCentipede support macOS 2.82 packages?

The archived 2.82 release lists Windows x64, Linux x64 and browser extension assets. Do not fill a missing macOS package with an unverified third-party build.

Can a browser extension bypass access restrictions?

Browser capture should only handle content that the account is allowed to access and save. Cookies, signed URLs and request headers can carry account permissions and must be handled as sensitive data.