Free Crypto Portfolio Trackers: What the Limits Really Mean

The signal

The useful comparison is a chain: what enters the application, what remains visible, what can be corrected and what leaves it. A single label such as unlimited can describe only one link. Treating it as a promise about the whole chain makes unlike products appear interchangeable.

DN reviewed ten official documents from CoinStats, Delta, Koinly and CoinLedger on 14 November 2026. The evidence establishes published features and limits. It does not establish import accuracy, uptime, customer support quality or investment performance.

1. Decide what the tracker must explain

Write a short inventory before comparing subscriptions: each exchange account, subaccount and public wallet address; the assets held; the earliest necessary date; and the output you want to retain. Distinguish accounts you own from addresses you follow. A watchlist of another wallet is not part of your own holdings, even if the application can display both.

Next define the result. A current balance tells you what a source reports now. A transaction history helps explain how it changed. A performance calculation adds assumptions about deposits, withdrawals, prices and timing. A tax report adds a separate classification and reporting framework. Buying access to one does not automatically supply the others.

This is where a spreadsheet can remain useful alongside an application. A small source inventory makes missing coverage visible without becoming a second full accounting system. Record whether a connector imports balances, trades, deposits, withdrawals or all of them. Do not mark an account complete solely because a connection succeeded.

DN’s existing exchange balance reconciliation guide explains the arithmetic of account-state differences. The question here is narrower: which documented product boundaries could prevent you from obtaining the record your workflow requires?

2. Free plans limit different objects

CoinStats lists Basic allowances of 10 portfolios, 20,000 transactions and 10 daily synchronisations per portfolio. Those are three separate constraints. Its pricing table shows 100 Premium portfolios, while the FAQ on the same page says unlimited. The help overview also gives 100. DN records that disagreement instead of selecting the more generous wording. [1] [2]

Delta’s September plan explanation advertises unlimited connections on its free tier, while restricting the assets that can be fully viewed. A separate help page permits one active portfolio on free and PRO, with multiple active portfolios reserved for PRO+. Connecting many sources therefore differs from organising them into several accessible portfolios. [4] [5]

Koinly’s help page permits unlimited wallets and 10,000 imported transactions on free, but says calculations halt above that threshold. It also excludes report generation. CoinLedger’s pricing page advertises unlimited free transaction tracking and wallet/exchange synchronisation, with full tax reports sold separately. Neither statement proves that every transaction type in your own history is supported. [7] [9]

The implication is practical. Count the object each provider actually meters. Ten addresses need not mean ten strategy portfolios; ten thousand fills need not become ten thousand records after a provider groups events. Do not compare limits until you have checked the applicable counting method. The smallest number in a pricing table is not automatically the tightest constraint.

3. Check what an export actually contains

CoinStats documents exports of transaction history or balances on web and mobile. Its paid-plan overview lists portfolio export as a Premium benefit; the documents reviewed do not establish an equivalent free entitlement. Confirm that entitlement before relying on a free account as your only retained record. [2] [3]

Delta documents CSV import, import summaries and the ability to replace or revert an imported file. Its normal export excludes manually deleted transactions. The portfolio-limit guide separately says disabled portfolios remain exportable. These details matter when reconstructing a historical correction rather than merely moving the currently visible rows. [5] [6]

CoinLedger explicitly permits free CSV transaction-history downloads, with account, asset and date filters. Ignored records are excluded by default. That file omits calculated capital gains and losses and is not the tax filing report. This is a useful example of portability being available while a different analytical output remains paid. [10]

Before you commit, write down the exact deliverable: native-asset movements, original identifiers, fee currency, timestamps, corrections and enough source information to trace each row. Keep a copy of the original provider export as well as any cleaned working file. A portable current view and a preserved change history are different requirements; choose deliberately rather than discovering the distinction during a migration.

4. Use a small fixture to expose the boundary

The following is a synthetic specification, not a test performed inside any of the four applications. Suppose an investor owns two exchange accounts and one self-custody wallet. Exchange A sends one unit of an asset; the wallet receives 0.99 units after a 0.01-unit network charge. Later, the wallet sends part of that holding to exchange B. One export is downloaded twice.

A useful import check asks whether the application keeps both sides of the owned transfers, recognises the fee once and identifies the duplicate file. It also asks what happens if the receiving record arrives late. Correct native-asset quantities should be evaluated before a changing market price is used to produce a combined currency value. This fixture is deliberately small enough that each expected movement can be inspected.

Koinly publishes matching conditions involving asset identity, timing, order, amounts and transaction hashes. Its guide also explains that moving between differently represented assets may not match as a simple transfer. That is evidence of a documented rule set, not proof that the software will classify every bridge or user transaction correctly. [8]

The buyer’s next step is an authorised trial using non-sensitive sample records where the provider permits it. Preserve the input file, selected options, software date, imported count and resulting export. If you cannot run that exercise, call your decision a documentation-based shortlist. Do not replace missing test results with a confidence score or a claim that automation is always more accurate.

5. Calculate when a transaction limit becomes relevant

The DN Transaction-Cap Runway tool estimates capacity for a plan with a stated transaction ceiling. It subtracts the imported history from that ceiling and divides the remaining capacity by an assumed daily rate. The daily rate is an input, not an observed trading forecast. For a genuinely uncapped plan, this calculation is unnecessary.

With a hypothetical 10,000-record ceiling, 9,200 existing records and 40 additional counted records a day, remaining capacity is 800 records, or 20 days at that rate. Raising the ceiling to 20,000 and the daily rate to 60 gives 180 days. These examples illustrate the arithmetic; they do not describe any reader’s account or predict how a named product will count their transactions.

The tool also reports records above the ceiling. At 10,500 against a 10,000 limit, the overage is 500 and remaining capacity is zero. A zero daily rate returns no time estimate rather than infinity. This avoids suggesting that a dormant account can never receive another record, correction or delayed import.

Use the output to schedule a review, not to decide which product is best. The numeric checks reject impossible counts and invalid denominators. They cannot determine whether an exchange’s trade count equals the tracker’s billable count, whether historical imports are complete, or whether a provider applies its ceiling to the same period. Those are prerequisites the user must establish.

6. A sensible choice can still be a free plan

A small, stable portfolio may need only a current overview and an occasional export. Paying for advanced analytics would add little if those are the actual requirements. Conversely, a low account count can conceal a large event history when frequent trading, distributions or automated actions create many records. Match the plan to the workload rather than to a label such as beginner or professional.

Delta may merit inspection when connection count and portfolio organisation are the key questions. CoinStats exposes separate published capacity and refresh limits. Koinly and CoinLedger may enter a shortlist when transaction history and eventual tax reporting must connect. These are routes for further verification, not a ranking of accuracy or an endorsement of one provider for every country.

Freshness has a cost as well as a benefit. A planning dashboard need not update at the same cadence as a trading terminal. Decide how old the information may be before it becomes unusable for your task, then verify the connector’s documented behaviour. Do not treat a daily synchronisation allowance as a promise that every refresh will complete successfully.

Also test the exit condition conceptually: what will you retain if you stop paying, disconnect a source or close the application account? The answer should include the data needed to continue elsewhere. A modest export that preserves interpretable records can be more useful than an elaborate dashboard that leaves the next reviewer unable to reconstruct the inputs.

7. Turn a shortlist into a reviewable decision

For each candidate, keep four answers together: the sources it can import, the limits that affect your use, the output you can export and the unresolved questions. Put a date beside each answer. If documentation conflicts, preserve both statements and ask which applies to the exact product and plan before making a purchase.

The alternative explanation is that limits rarely bind for ordinary users and that the interfaces handle most common transfers adequately. That may be true for a particular portfolio. It does not remove the need to establish coverage; it means a small, inexpensive verification exercise may be sufficient. A complex testing programme is unnecessary when the requirement and evidence are simple.

The decision changes when a previously unsupported asset, missing export field or inaccessible portfolio becomes essential. It also changes if a provider revises limits or resolves a documented conflict. Record those triggers rather than treating a comparison published today as a permanent recommendation.

The useful outcome is a justified shortlist and a retained record of why it fits. It is possible to reach that outcome without paying, without ranking products by an invented score and without pretending that a documentation review was a live test.

The evidence, side by side

DN Transaction-Cap Runway

Illustrative capacity scenario; no account is connected and defaults are not observed user data.

Finite numeric inputs; ceiling a positive integer; history a non-negative integer; daily additions non-negative. Numeric maxima are input guards, not provider limits.

Cannot verify billing definitions, import completeness, actual plan eligibility or future growth. Not needed for an uncapped plan.

Scenarios to watch

Stable history

Hypothetical

A small source inventory and infrequent additions fit a documented free allowance. Review export access rather than upgrading solely for an AI label.

Growing history

Hypothetical

Many recorded events consume capacity even when the number of accounts stays constant. Use the runway estimate to schedule a plan review.

Unresolved documentation

Observed evidence limit

CoinStats Premium portfolio language differs between the pricing FAQ and table/help. Confirm the applicable allowance before depending on it.

Method and limitations

DN opened ten official pricing and help documents on 14 November 2026 and compared import capacity, visible portfolio access and export scope. The panel contains four named providers chosen to contrast portfolio applications with transaction/tax-oriented services; it is not a census or a ranked market survey.

Publication dates are copied only where the page displays them. Undated pricing pages retain a null source date. CoinLedger’s reviewed pricing page still labels available tax-report years 2010–2025; this article makes no claim that a 2026 filing product was already available.

No account was created, wallet connected, subscription bought or file imported into a provider. The multi-source fixture is a proposed verification exercise. Only the local calculator arithmetic was executed; its receipt records default, changed-input, boundary and invalid-input checks.

Published feature descriptions are provider claims. They do not establish reliable operation or accurate classification on a reader’s data. Product coverage, entitlements and regional availability can change.

This article does not calculate tax, certify custody or assess whether an asset is appropriate to own. It compares the records a reader may need and the documented boundaries of obtaining them.

Primary sources and evidence register

Source dates and reporting periods differ. Several documents from one issuer are one source family, not independent confirmations. The evidence download contains the observations used in this article.

Frequently asked questions

Does unlimited connections mean unlimited usable portfolios?

No. Those terms can measure different objects. Delta’s documents separate connection count from active portfolios, so inspect the plan definition rather than extrapolating from one allowance.

Is a free transaction CSV the same as a tax report?

No. CoinLedger’s documented free history export omits calculated gains and losses and is not its filing report. Verify the contents of each export you intend to use.

Did DN test these applications with real accounts?

No. This is a comparison of official documentation accessed 14 November 2026. The illustrative fixture was not uploaded to providers. The local arithmetic calculator was tested separately.

Can the calculator tell me which plan to buy?

No. It estimates capacity under your stated ceiling and rate. You must establish what the provider counts, the relevant period and whether the required imports and exports are supported.