The files behind the record

Keep the receipt with the service.

Add a JPEG, PNG or PDF to the relevant service record. The original bytes stay in this browser until you choose to download or share a copy.

Keep a complete private copy

Save commits records and files together. Download the full private ZIP for a portable copy of all bikes, records, plans, notes and original files. Restore that ZIP in the browser and save again. The separate text-only JSON file remains compatible with the native development app; it contains no attachments.

Choose what travels

Files start excluded from handovers. Select individual files within the current bike, review the text and file list, then download the selected handover ZIP. The ZIP uses neutral filenames and retains each file’s service date and component association. Private-note fields, plans and unselected files are excluded.

Selected originals are not redacted: receipts and images can contain addresses, payment details or embedded location metadata. Download and inspect an original before sharing it. Plain-text handovers and print/PDF contain no attached files.

Practical limits

Two files per record, 20 across the collection, 5 MiB per file and 30 MiB in total. Images are checked for decoding with a 40-million-pixel limit when attached. PDFs are retained as original downloads and are not embedded in the tool. File headers and hashes check consistency, not authenticity or safety.

A local record

No cloud account, automatic sync or proof of ownership. Older text storage stays in the browser after migration; the new file collection becomes the active copy. Clearing this site’s browser data removes both, including any private recovery archives. Downloaded copies remain separate.