Users who prefer Free Download Manager's features (download acceleration, BitTorrent support, resume broken downloads, traffic management) over the browser's built-in download manager need a way to seamlessly route downloads to FDM

1. User installs the FDM extension and the required native client on their system. 2. When browsing, downloads are automatically intercepted (when toggle is active) or manually sent via right-click context menu. 3. The extension pauses the browser's built-in download and sends the URL to FDM via native messaging. 4. FDM handles the actual download with its acceleration, scheduling, and management features. 5. Users can configure the executable path, arguments, MIME exclusions, and hostname whitelist in the options page.

Target users: Power users who use Free Download Manager for download management / Users who want download acceleration and BitTorrent support via FDM / Users who need to resume broken downloads across sessions

Cannot verify whether FDM itself has any paid/pro tiers in its desktop application (the extension itself has none)
Cannot inspect the native client code as it's hosted externally on GitHub

Monetization

No paid features detected

No paid features, premium tiers, subscriptions, payments, or gating mechanisms exist in the extension. All keyword hits for 'pro' are CSS progress bar classes or JavaScript Promise objects, not 'pro' plan features. All 'license' hits refer to open-source licenses (MIT, Mozilla Public License). All 'stripe' hits are CSS table.striped classes. The only monetary element is an optional 'Support Development' donation link in the options page (data/options/index.js line 118: '&rd=donate'), which is voluntary support, not a feature gate. FDM itself is free open-source software under GNU GPL.

Confidence: 95
Payment platform: --
Source: AI / High
Login required: No
Reason: No login, sign-in, authentication, or account creation flow exists in the extension. The extension communicates with a locally installed Free Download Manager desktop application via Chrome native messaging (chrome.runtime.sendNativeMessage). No user credentials are collected or transmitted anywhere. The only 'account' keyword hit is from a third-party library comment ('Account for wraparound' in materialize.js line 11107), which is irrelevant.

Permission risk

High-risk permissions

This estimate uses declared permissions and host permissions to assess access scope and sensitivity.

敏感权限：nativeMessaging
扩展能力较强：storage、downloads、activeTab、scripting

Publisher

InBasic

Independent publisher

Email: [email protected]
Phone: --
Address: --

Public contact fields are shown above. Developer portfolio pages are available on paid accounts.

View developer portfolio

Permissions

Host access