If you are researching FingerprintJS pricing, the first thing to untangle is that "FingerprintJS" is two different products with two different pricing models. There is the free, open-source library, and there is the commercial product, now branded Fingerprint (formerly FingerprintJS Pro), which is priced per API call. Confusing the two is the most common reason a pricing estimate comes out wrong.
This guide explains both, using Fingerprint's publicly known pricing as of 2026, and shows where a transparent, published alternative like cside lands on cost.
The two things called "FingerprintJS"
Before any numbers, split the name:
- The open-source library (FingerprintJS). A browser-only JavaScript library you self-host. It is free to run, now under a Business Source License (BSL), which allows development use but restricts some production use. There is no per-call fee because there is no hosted service, you host it yourself and accept a lower identification accuracy than the paid product.
- The commercial product (Fingerprint, formerly FingerprintJS Pro). A hosted device-identification API with server-augmented matching, priced per API call across Pro, Business, and Enterprise tiers. This is what most people mean when they ask about "FingerprintJS pricing".
The two share a name and a heritage but not their accuracy or their cost model. Replacing one is a different exercise from replacing the other.
FingerprintJS open-source library pricing: free
The open-source library carries no license fee and no per-call cost. You install it, host it, and run it yourself. The trade-off is accuracy: the free browser-only library reaches a lower identification rate than the paid, server-augmented product, and the move to a Business Source License makes some teams reluctant to build a long-lived production dependency on it. If your only constraint is budget and browser-only accuracy is enough, the library is genuinely free.
Fingerprint Pro pricing: per API call
The commercial product is where "pricing" gets real. Fingerprint publishes a per-API-call model. As of 2026:
- Entry paid plan (Pro): around $99 per month, including 20,000 API calls.
- Overage: $4 per 1,000 additional API calls.
- Business and Enterprise: higher included volume plus features such as broader data retention, SSO, and support, priced on a custom quote.
Fingerprint also offers a limited free plan for very low volume and trials, but the paid Pro plans do not include a perpetual free allowance the way an always-on free tier does. Once you pass the free limits, you are on per-call billing.
The number that matters is the per-call structure. Every visitor identification is one API call. That is predictable and cheap for low-frequency decision points, a login, a checkout, a signup, and much less predictable for a high-traffic consumer site where every page view triggers a call.
What "per API call" actually costs you
The entry price tells you almost nothing on its own. To estimate real spend, you need two more numbers: the included call volume and the overage rate. A plan with a low headline price and a high overage rate can cost more than a plan with a higher headline price and a generous allowance, once your traffic is real.
Work it through with a concrete figure. Suppose you make 500,000 API calls beyond your included volume in a month:
- On Fingerprint Pro at $4 per 1,000 overage, that is roughly $2,000.
- On cside at $2 per 1,000 overage, the same 500,000 calls is roughly $1,000.
Same identification job, half the marginal cost. The entry prices are nearly identical; the economics diverge as you scale.
FingerprintJS pricing at a glance
| Product | Model | Entry price | Included calls | Overage | Free tier |
|---|---|---|---|---|---|
| FingerprintJS (open-source library) | Self-hosted, BSL | Free | n/a | n/a | Free (self-host) |
| Fingerprint Pro (commercial) | Per API call | ~$99/mo | 20,000 | $4 / 1,000 | Limited free plan; no perpetual allowance on Pro |
| cside | Per API call | $99/mo | 50,000 | $2 / 1,000 | 1,000 calls/mo, forever, no card |
Figures are Fingerprint's and cside's publicly available pricing as of 2026; check each vendor's pricing page for the current numbers.
The cost the price tag hides: an ID vs a verdict
Per-call pricing is only half the cost conversation. The other half is what each call returns. A Fingerprint visitor ID answers "who is here". It does not, on its own, tell you whether the visitor is an AI agent, whether the session is running through a VPN or proxy, or whether it is incognito. If your real problem is fraud, you buy the identification and then buy the decisioning separately, a second contract, a second integration.
That is why comparing FingerprintJS pricing purely on dollars-per-call can mislead. The honest comparison is dollars per call for the outcome you actually need.
cside pricing: a transparent alternative
cside publishes its plan openly and is built so one per-call spend covers more than an ID:
- Free tier. 1,000 API calls per month, forever, no credit card. Enough to validate accuracy on your own traffic before you pay.
- Business plan. $99 per month including 50,000 API calls, with overage at $2 per 1,000.
- Enterprise. Custom quote, adding chargeback fingerprinting, 90-day data retention, and SSO.
For that spend, cside returns a device fingerprint across 250+ browser, device, and network signals at 99.7% accuracy, and a real-time verdict: AI agent and bot detection, VPN and proxy detection, and incognito detection, all from a single first-party JavaScript snippet loaded from your own origin. Fingerprint publishes a separate 100+ signals figure for its own product; the two counts measure each vendor's own capture and are not interchangeable.
cside's native iOS and Android SDKs are in beta (early access), running the same engine as the web client with app-only signals on top. Fingerprint's mobile SDKs are generally available across Android, iOS, React Native, and Flutter, so if GA mobile breadth is a hard requirement, that is a point in Fingerprint's favour.
cside vs Fingerprint Pro: pricing side by side
| cside | Fingerprint Pro | |
|---|---|---|
| Entry price | $99/mo | ~$99/mo |
| Included API calls | 50,000 | 20,000 |
| Overage per 1,000 | $2 | $4 |
| Free tier | 1,000 calls/mo, forever, no card | Limited free plan; no perpetual allowance on Pro |
| 500K extra calls/mo | ~$1,000 | ~$2,000 |
| Signals per session | 250+ | 100+ |
| Returns a fraud verdict | Yes (AI agent, VPN/proxy, incognito) | Partial (bot signal) |
| Collector | First-party (your origin) | Third-party origin |
| Mobile SDKs | Beta (native iOS, Android) | GA (Android, iOS, React Native, Flutter) |
For the full side-by-side, see the cside vs Fingerprint comparison, and for the wider market the FingerprintJS alternatives survey.
Which pricing model fits you?
- Budget is the only constraint and browser-only accuracy is enough: the free open-source FingerprintJS library, self-hosted, accepting the BSL terms and the accuracy gap.
- You need the highest raw identification accuracy and GA mobile SDKs, cost no object: Fingerprint Pro, on its per-call plan.
- You want a transparent per-call plan, a free tier to validate first, and a fraud verdict (not just an ID) from one first-party script: cside, at $99/month for 50,000 calls with $2 per 1,000 overage.
If you are choosing on cost, the practical move is to validate on real traffic before you commit. cside's free tier lets you do exactly that, and the sibling guide to the best FingerprintJS alternatives ranks the wider field if identification is only part of your problem.
