ThumbmarkJS and FingerprintJS are the two best-known MIT-licensed browser fingerprinting libraries, and both sell a paid API on top. This guide compares the open-source packages and the hosted tiers side by side, with verified install code, pricing, and a pick-by-scenario table.
TL;DR verdict
ThumbmarkJS and FingerprintJS are close cousins. Both open-source packages are MIT-licensed, run entirely in the browser, and return a hash derived from browser attributes. Both vendors also sell a hosted API that adds server-side processing and a server-generated visitor ID. The decision is usually less about the free library and more about which paid tier you might grow into.
For the free, local-only library, the two are broadly interchangeable: pick on bundle fit, API style, and release cadence. For the hosted tier, ThumbmarkJS has the lower entry price (a free API tier, then EUR 15 per month), while Fingerprint Pro is the older, more established platform with a published enterprise SLA and a documented per-plan retention window. Both vendors say plainly that the client-only library is the less accurate option, so neither open-source package should be treated as a fraud-grade identifier on its own.
This is an independent comparison written by the team behind Benny the Doorman, a third option covered briefly near the end. All pricing and accuracy figures below are the vendors' own statements, checked on 2026-10-23.
At a glance
| ThumbmarkJS | FingerprintJS | |
|---|---|---|
| npm package | @thumbmarkjs/thumbmarkjs | @fingerprintjs/fingerprintjs |
| Latest version checked | v1.12.0 (2026-09-25) | v5.3.0 (2026-10-07) |
| Open-source license | MIT | MIT |
| Maintenance | Roughly monthly releases | Active; last commit 2026-10-21 |
| Open-source output | Thumbmark hash plus component breakdown | visitorId hash plus component list |
| Accuracy as stated by the vendor | ~80% uniqueness (open source), over 99% (API) | OSS accuracy "significantly lower" than the commercial version; commercial described as industry-leading |
| Hosted API | ThumbmarkJS API, with a free tier | Fingerprint Identification (Pro), closed source |
| Hosted API entry price | Free up to 1,000 calls/month, then EUR 15/month for 15,000 calls | Free up to 1,000 calls/month, then $99/month for 20K calls |
| Overage | EUR 1 per extra 1,000 calls | $4 per 1,000 calls |
| Enterprise | Custom, from 1M+ calls | Custom, 99.9% SLA |
Install and usage: ThumbmarkJS
ThumbmarkJS installs from npm as @thumbmarkjs/thumbmarkjs. It needs browser APIs, so the call must run client-side (in a framework like Next.js, inside an effect rather than during server rendering). The snippet below follows the ThumbmarkJS npm usage guide.
// npm install @thumbmarkjs/thumbmarkjs
import { Thumbmark } from '@thumbmarkjs/thumbmarkjs';
const tm = new Thumbmark();
const result = await tm.get();
console.log(result.thumbmark);
// Optional: pass an API key to enable server-side signals and a visitor ID
// const tm = new Thumbmark({ api_key: 'YOUR_API_KEY' });ThumbmarkJS: construct a Thumbmark, then call get(). Per the README, the api_key option enables server-side signals and visitorId.
Install and usage: FingerprintJS
FingerprintJS installs as @fingerprintjs/fingerprintjs. The README recommends loading the agent once at application startup and calling get() when the identifier is needed. Its CDN snippet notes that ad blockers and some browsers can block the CDN import, so the npm package is the safer route.
// npm install @fingerprintjs/fingerprintjs
import FingerprintJS from '@fingerprintjs/fingerprintjs';
// Initialize the agent at application startup.
const fpPromise = FingerprintJS.load();
(async () => {
// Get the visitor identifier when you need it.
const fp = await fpPromise;
const result = await fp.get();
console.log(result.visitorId);
})();FingerprintJS OSS v5: load() once, then get() on demand. Taken from the project README.
Open-source tier comparison
On the free side the two libraries do the same job in the same place. Each reads browser attributes on the client, hashes them, and returns an identifier with no backend and no account. Both are MIT-licensed and commercially usable, so licensing is not a differentiator.
The differences are practical. ThumbmarkJS exposes a constructor with options to include or exclude components, set a timeout, and apply a stabilize preset aimed at keeping the hash steady across private browsing and iframes. It also ships a small amount of opt-out sampled logging, documented in its README, which security-conscious teams should read and, if needed, disable with the logging option. FingerprintJS OSS has a longer history and a larger installed base, and its documentation carries a migration guide between major versions.
Both projects are candid about the ceiling. ThumbmarkJS states that its client library reaches roughly 80% uniqueness across general browser populations and that Mac and Safari users can see higher collision rates. FingerprintJS states that browser-side accuracy is significantly lower than its commercial product and that client-generated fingerprints are vulnerable to spoofing and reverse engineering. Treat either as a signal, not as proof of identity.
Paid tier comparison
| Plan | ThumbmarkJS API | Fingerprint Pro |
|---|---|---|
| Free | 1,000 calls/month; advanced fingerprint with server-side signals (TLS, HTTP headers, network) | $0 up to 1,000 API calls/month; 14-day Pro Plus trial; 500K free Android calls/month |
| Mid tier | Pro: EUR 15/month for 15,000 calls, then EUR 1 per extra 1,000 | Pro Plus: $99/month for 20K calls, then $4 per 1,000 |
| Top tier | Enterprise: custom, from 1M+ calls | Enterprise: custom, 99.9% SLA |
| Visitor ID | Server-generated Visitor ID with the paid API (not in the open-source library) | Stable server-side visitor identifier |
| Data retention | Not verified | 7, 30, or 90 days depending on plan |
| Extra signals | Pricing page lists bot, VPN, and datacenter detection, threat level, and webhooks; per-plan breakdown not verified | Smart Signals such as bot, VPN, and tampering detection; full platform trial for 14 days |
What the paid tiers add over the open-source libraries
Both vendors move the hard part to a server. The ThumbmarkJS API combines the client signals with server-side analysis such as TLS handshake details, HTTP headers, and connection-level data. Fingerprint's commercial product likewise pairs client collection with server-side processing and network-level data the browser cannot see, and says that processing also validates that signals have not been tampered with or replayed.
That server step is the real upgrade. It is why a hosted visitor ID can be more stable and harder to spoof than a purely client-side hash, and it is also why the hosted tiers add a third-party dependency, a per-call bill, and data flowing to the vendor. Fingerprint Pro is closed source, so the server logic cannot be audited by customers.
On cost, the two are easy to model. At 15,000 monthly identifications ThumbmarkJS Pro is EUR 15, while Fingerprint Pro Plus is $99 for its first 20K calls. At higher volumes the overage rates (EUR 1 versus $4 per 1,000) widen the gap, though the platforms are not feature-identical and Fingerprint's higher price buys a longer-established product, an SLA at the enterprise tier, and native mobile coverage. Always price your real call volume against each vendor's current page.
Which to pick by scenario
| Scenario | Better fit |
|---|---|
| Free local hash, no backend, MIT license | Either; choose on API style and bundle fit |
| Prototype or hobby project that may need a hosted API later | ThumbmarkJS (free API tier and lower first paid step) |
| Fraud-grade identification with a vendor SLA | Fingerprint Pro (published 99.9% enterprise SLA) |
| Native iOS and Android coverage from one vendor | Fingerprint Pro (iOS, Android, and Flutter SDKs) |
| Smallest possible monthly bill at 10K to 20K identifications | ThumbmarkJS Pro, subject to your feature needs |
| Closed-source server logic is a procurement blocker | Neither hosted tier; consider a client-only library |
| Maximum community history and documentation | FingerprintJS |
Where CreepJS fits
Searches for "creepjs vs fingerprintjs" often compare tools that serve different purposes. CreepJS is an MIT-licensed research project, not a production library: it has no versioned releases, its last commit was in June 2026, and its output is a detailed trust report rather than an ID you store. Use it to see how a browser looks to a detector, then pick a maintained library for production. Use only the official site at [abrahamjuliot.github.io/creepjs](https://abrahamjuliot.github.io/creepjs); the project's README warns that other domains are malicious mirrors. For a fuller comparison, see [Benny vs CreepJS](/vs/creepjs).
If you need a cross-browser device ID
A per-browser hash from either open-source library changes when the same person switches from Chrome to Safari. If that matters, one route is a hosted visitor ID from Fingerprint Pro or the ThumbmarkJS API. A third option is Benny the Doorman, which returns a per-browser fingerprint and a separate hardware-bound fingerprint client-side. Benny is free but closed-source, so it does not match the MIT terms of the two libraries above. It also has no hosted visitor-history database, so it is not a one-for-one replacement for a paid API. Side-by-side pages: [Benny vs ThumbmarkJS](/vs/thumbmarkjs) and [Benny vs FingerprintJS](/vs/fingerprintjs).
Related reading
For a wider field, see [FingerprintJS alternatives](/blog/fingerprintjs-alternatives), the [best browser fingerprinting libraries](/blog/best-browser-fingerprinting-libraries), and the roundup of [open-source fingerprinting libraries](/blog/open-source-fingerprinting-libraries). Browser fingerprinting is regulated in many jurisdictions, so review the legal side before shipping; see [is browser fingerprinting legal](/blog/is-browser-fingerprinting-legal). This is engineering guidance, not legal advice.
Frequently asked questions
Is ThumbmarkJS better than FingerprintJS?
Neither is strictly better. The open-source libraries are both MIT-licensed, client-side, and broadly interchangeable. ThumbmarkJS has a lower-priced hosted API, while Fingerprint Pro is a more established platform with a published enterprise SLA. Test both against your own traffic.
Is FingerprintJS free?
The open-source @fingerprintjs/fingerprintjs library is free under the MIT license. The commercial Fingerprint Pro product has a free plan of up to 1,000 API calls per month, then paid plans starting at $99 per month for Pro Plus, as listed on fingerprint.com/pricing on 2026-10-23.
How much does ThumbmarkJS cost?
The open-source library is free. The hosted ThumbmarkJS API has a free tier of 1,000 calls per month, a Pro plan at EUR 15 per month for 15,000 calls then EUR 1 per extra 1,000, and custom Enterprise pricing from 1M+ calls, according to thumbmarkjs.com/pricing on 2026-10-23.
How do I install ThumbmarkJS from npm?
Run npm install @thumbmarkjs/thumbmarkjs, import { Thumbmark } from the package, create a new Thumbmark(), and call its get() method in the browser. The result includes the thumbmark hash. It cannot run server-side because it needs browser APIs.
How accurate is FingerprintJS open source?
FingerprintJS states that its open-source accuracy is significantly lower than its commercial version and that browser-side fingerprints are vulnerable to spoofing and reverse engineering. It does not publish a single uniqueness percentage for the open-source package, so measure it on your own audience.
Is CreepJS a FingerprintJS alternative?
CreepJS is a research and detection project, not a production identification library. It has no versioned releases and outputs a trust report rather than a stable ID. It is useful for studying how detectable a browser is, but not as a drop-in replacement for FingerprintJS.
Get started
Need a device ID that survives a browser switch?
Benny the Doorman is free, not open source, and returns a per-browser fingerprint plus a cross-browser hardware fingerprint in one client-side call.
Last reviewed November 17, 2026

