Save bike fit measurements: local records, exports and backups

The bicycle passport is a saved profile describing declared bicycle values and their references. A dated passport copy is a separate history entry made from an opened saved source. A fit session is another record type, with its own context and possible links to reduced pose series or optional video. Saving one of these does not silently create all the others. A new date on a copied profile does not mean that somebody measured the bicycle again.

Browser data belongs to a particular site origin and browsing context. The public app does not provide account-side synchronisation of these core records. A browser account, a bookmark or an installed shortcut is not an OpenBikeFit archive. MDN describes origin-based storage, best-effort retention and different private-browsing behaviour. Retention can be affected by browser policy or user removal; no fixed lifetime or private-mode diagnosis follows from an empty list alone.

Imagine a fictional bicycle named Workshop example. At 08:00 its saved saddle-height entry is 740 mm under a named reference. At 08:10 a dated passport copy records that same opened value. Nobody has taken a new physical observation in this example. At 08:20 the user prepares a private archive and reviews its inventory; the prepared file holds the saved records read for that preparation, not a live connection to the bicycle or future edits.

At 09:00 a separately documented observation may lead the user to save a different profile value. Neither the 08:10 history entry nor the already prepared 08:20 file is rewritten to contain that later edit. Their earlier dates remain meaningful. Do not relabel the old file as a current complete record or overwrite the only earlier copy merely to tidy a folder. If the later state must be retained, deliberately prepare and verify a new appropriate copy with a distinguishable date.

For a bicycle-profile JSON file, choose Import bike profiles in My bikes or Settings. Its supported limit is 100 profiles and 1,000,000 bytes. Review the file and choose the intended profiles; the deliberate import makes new local IDs and copies, never replaces an existing bicycle. Importing the same profile file again can create more copies. It is not a way to synchronise changes back into the original profile.

For a supported complete or no-video archive, choose Recover saved records from a complete archive in Settings. The implemented byte limit is 64 × 1024 × 1024: 64 MiB, or 67,108,864 bytes. Some existing interface text rounds that label to “64 MB”; it is not a decimal 64,000,000-byte contract. A profile JSON, CSV, calculator link or rescue note does not become a supported complete archive by changing its extension or filename.

Complete-archive recovery adds the six database collections together in one transaction. Existing records are never replaced. An ID or key collision, or a link that would connect an archived object with a separate local record, rejects the whole addition. This is why importing the same archive twice is not a normal incremental update. A collision is not an instruction to rename internal IDs or remove the destination records.

Save an appropriate copy of the destination’s current records before any later deliberate recovery. Browser preferences, consent receipts and unfinished workflow drafts can be present in an export but are not imported into the destination. The recovery action has a 30-second saving limit and requests cancellation until commit. A completed commit cannot be undone by Cancel. If the outcome remains unconfirmed, follow the existing reload-and-inventory boundary rather than repeating the write or claiming a rollback.

Some failed or conflicted session changes are held only in the open tab. Settings pauses archive preparation and recovery while the relevant pending session or intake-revision copies exist. Return to that original workflow and read its recovery notice. Where provided, Download unsaved records or Download held session records preserves a separately scoped session copy; it is not the complete archive and does not contain pose landmarks or raw video.

Do not assume that every kind of tab memory has the same rescue action. In particular, an open dated-passport proposal is not automatically a saved history event or part of an archive. Leaving or reloading can lose a RAM proposal; an already dispatched native save may nevertheless finish. Keep the confirmed saved state separate from an unconfirmed or rejected proposal and follow the existing manual recovery action, without treating all open tabs as backed up.

An exported JSON file is not encrypted by this export workflow. It can contain bicycle notes, entered values, session context, reduced movement records and optional videos according to its kind. Store it only where the intended people have access. A download folder may be included in a separate device backup or synchronisation service under its own settings; that is different from OpenBikeFit providing account sync. Do not attach a complete rider or client archive to a general business inquiry.

Clearing the site, closing the guide or discarding an in-tab review cannot recall a printed, copied, downloaded or shared record. Chrome’s help distinguishes website storage from downloaded-file history; deleting a history listing is not a secure file-removal workflow. Decide recipients and retention for actual files separately. This guide does not perform deletion, configure a backup provider, make a confidentiality guarantee or replace your responsibilities for other people’s records.

For a paper-first measurement, read the blank worksheet. For one saved bicycle, open My bikes or its setup card and inspect the current source. For a broader saved-data copy or supported archive review, open Settings. The fixed links carry no entered measurements, IDs or example records, and none starts export, import, printing or deletion. Existing pages can still read their own local state when deliberately opened.

Finally, keep documentation and physical decisions separate. An exported or restored value remains a recorded declaration with its original references, not a newly measured coordinate, component compatibility check, installation certificate or fit approval. A real bicycle may have changed after the record was made. Use current physical observations and exact component instructions for that later task; preserving an honest record is valuable without claiming it settles the task itself.