18+ Informational · Not affiliated with any platform

CamToken Calculator

Methodology

How we calculate, and what we don't know

Every figure on this site comes from one data file and a small set of tested functions. Here is exactly how they work.

1. Two different prices for one token

Every platform has two numbers per token. The creator token value is what a creator gets paid per token under the platform’s payout system. The viewer token cost is what a viewer pays per token when buying a bundle. They are never the same, and this site never uses one in place of the other.

2. Creator maths

creator earnings = tokens × creator value per token

Example: 5,000 × $0.05 = $250.00. To avoid floating-point errors, rates are turned into integer micro-dollars and amounts are rounded half-up to the cent only for display. Reverse mode divides the target by the rate and rounds up to whole tokens, so the target is always reached: $1,000 ÷ $0.05 = 20,000 tokens.

3. Viewer maths: cheapest package combination

Multiplying tokens by an average price would be wrong for viewers, because tokens are sold in fixed bundles. Instead we solve the problem “buy at least N tokens for the lowest total price” using unlimited copies of each listed bundle:

  1. Bundle sizes are divided by their greatest common divisor to shrink the search.
  2. The bundle with the lowest price per token pre-fills most of a very large order. This is provably safe: an optimal basket never needs more than (b − 1) of the other bundles, where b is the best bundle’s size in those units.
  3. The remaining amount is solved exactly with dynamic programming in integer cents. Ties go to fewer leftover tokens.

This runs in milliseconds in the browser and is checked against a brute-force solver in our unit tests. We also show the effective cost per token you wanted (total ÷ requested), which includes the cost of any leftover tokens.

4. “Where does a tip go?”

When a viewer tips, we don’t know which bundle the tokens came from. So we show a range: tokens × the lowest bundle price per token, up to tokens × the highest. The gap between that and the creator value is labelled the difference between estimated viewer purchase cost and creator token value. We deliberately do not call it platform profit. Payment processing, taxes, chargebacks, affiliate commissions, fraud and regional pricing are all unknown to us.

5. Currency conversion

Platforms price bundles and payouts in USD, so all token maths is done in USD. EUR, GBP, CAD, AUD and INR are converted only for display, using fixed reference rates (as of September 25, 2026) stored separately from platform data. Currency conversion is approximate; your bank or card issuer will use its own rate and fees.

6. Sources and confidence labels

We prefer sources in this order:

  1. Official platform documentation
  2. Official help and support pages
  3. Official model documentation
  4. Established secondary sources, only where official information isn’t publicly available

Platforms often show bundle prices only after sign-in, and vary them by country, account and payment method. So each platform carries a viewer pricing label:

  • Viewer prices: exact from an official, publicly visible price list.
  • Viewer prices: estimated · may vary from recent, consistent secondary snapshots; checkout may differ.
  • Viewer prices: varies · rough guide incomplete or inconsistent data; a rough guide only.

Creator rates are labelled confirmed, tiered (depends on the account) or conflicting (sources disagree; we show the range and a middle default). We never invent a price. If we can’t confirm one, we leave it out.

7. What this calculator does not include

  • VAT, GST or sales tax added at checkout
  • Promotions, first-purchase bonuses, memberships and loyalty rewards
  • Payout-method fees, currency conversion fees and income tax for creators
  • Studio or agency splits, contests and performance bonuses

8. Updating the data

Platform figures live in src/data/platforms.ts and exchange rates in src/data/currencyRates.ts. Every page, calculator, sitemap entry and redirect is generated from those files, so a change applies everywhere.