The text a change log records, and change history shows, in place of a binary field's base64
value: [binary: 6,144 bytes]. The bytes themselves stay in the record snapshot
(FullRecordJSON), which restore reads; only the per-field diff (ChangesJSON) and its
on-screen rendering use this, so a change to an embedding or a file is visible without carrying
the content twice more per save. Invalid base64 is reported as such rather than thrown on.
The text a change log records, and change history shows, in place of a binary field's base64 value:
[binary: 6,144 bytes]. The bytes themselves stay in the record snapshot (FullRecordJSON), which restore reads; only the per-field diff (ChangesJSON) and its on-screen rendering use this, so a change to an embedding or a file is visible without carrying the content twice more per save. Invalid base64 is reported as such rather than thrown on.