Know what the backup contains
The tracker exports a version-1 JSON file containing holdings and a last-saved timestamp. Each row includes an identifier, asset label, units, average cost and manual price. It is a data file, not a wallet backup, private-key export or exchange statement.
The tool provides no account or automatic cloud backup. Browser data can be cleared or unavailable. Keep exported files in storage you control and treat quantities and cost information as private. The export is plain JSON, not encrypted by the tracker.
Evidence: CryptoTrades manual portfolio tracker
Make a safe restore rehearsal
Export the current holdings before editing anything and keep the original file. For a rehearsal, use a separate empty browser profile at the same site origin, enter fictional data, export it and import the test file. Compare labels, units, costs, prices and totals after the restore.
Import adds accepted rows to existing holdings and gives imported rows new identifiers. Importing a file with two holdings into a tracker already containing those two holdings yields four rows; it is not an update or deduplication operation. Review duplicates before interpreting totals.
Evidence: CryptoTrades manual portfolio tracker
Respect the file and row limits
The importer requires version 1, a file no larger than 100,000 bytes and at most 100 holdings after the merge. Invalid numeric values, unsupported labels or duplicate identifiers within the incoming list can cause validation to reject it.
Do not delete the only working portfolio merely to test restoration. If import fails, preserve the file and compare its format with a fresh fictional export. Never include passwords, recovery words or API keys in a portfolio file or a support request.
Evidence: CryptoTrades manual portfolio tracker
Record the observation time outside the save timestamp
“Last manually saved” records a tracker save, not when every asset price was observed. Editing a quantity or importing old prices can produce a new save time without making those prices current. The current tracker has no per-row price-source or observation-time fields.
Keep a companion note with asset, source, quote currency and observation time. Before comparing values, check missing prices, unusually old observations, accidental decimal shifts and inconsistent quote currencies. No universal age threshold suits every use; state the window chosen for the exercise.
Evidence: CryptoTrades manual portfolio tracker
See how one stale value changes the total
In an invented two-row portfolio, two units of ALPHA marked at $100 contribute $200; three units of BETA at $20 contribute $60. Total value is $260. Updating ALPHA’s manual price to $90 gives $240, a $20 change with no sale or purchase.
Exporting after that edit preserves the new inputs, not independent proof that $90 was an executable market price. Keep the prior snapshot if the comparison matters. Backups support recovery and reproducibility; they do not validate custody, ownership or market accuracy.
| Snapshot | ALPHA value | BETA value | Total |
|---|---|---|---|
| Before refresh | $200 | $60 | $260 |
| After manual refresh | $180 | $60 | $240 |
Sources & method
- CryptoTrades manual portfolio tracker
Implementation checked locally: manual values, browser storage, additive JSON import; no realized-gain ledger. Checked 2026-10-29.
Continue learning
Found an error? Contact the editorial team with the page and supporting source. Never send private account information.