The replay file format

A replay is a plain JSON file anyone can read, so a reader never has to take this site's word for anything. This page describes version 1 of the format and the rules behind every figure the reader shows.

The file

Replay files are UTF-8 JSON and end in .writing-replay.json. The editor writes one edit per line, so a file is easy to read in any text editor.

{
"format":"writing-replay",
"version":1,
"how_to_open":"Open https://theguysaccount.github.io/proof-of-human-writing/verify/ and choose this file ...",
"app":"https://theguysaccount.github.io/proof-of-human-writing/",
"title":"My essay",
"author":"Sam",
"exported":"2026-11-10T08:31:00.000Z",
"tick_ms":50,
"final":{"length":687,"sha256":"1752c748…"},
"sessions":[
{"start":"2026-11-09T19:02:11.000Z","events":[
[114,0,0,"T"],
[3,1,0,"h"],
[7,2,0,"PASTED TEXT",2],
[4,12,11,""]
]}
]
}

Fields

Edits

Each event is [dt, pos, del, ins] or [dt, pos, del, ins, origin]:

OriginMeaningBrowser input types
0one key press: a single character, or a deletioninsertText, insertLineBreak, deleteContentBackward and other insert…/delete… types
1several characters at once from the keyboardthe same types with more than one character (word suggestions, swipe typing, dictation, insertReplacementText)
2pasteinsertFromPaste, insertFromPasteAsQuotation, insertFromYank
3drag and dropinsertFromDrop
4undo or redohistoryUndo, historyRedo
5a change with no trusted keyboard eventchanges made by scripts or extensions, events the page itself generated, and unknown types

Input types are defined in the W3C Input Events specification (MDN summary). The editor reads them from the browser; it never sees which keys were pressed.

How the reader marks the finished text

Each character of the finished text carries the origin of the edit that inserted it. One exception: when a paste, drop, undo or redo inserts text that was already in the document, or was removed from it earlier in the recording, the inserted characters keep the marking they had. That way a writer moving their own sentence around isn't counted as pasting, and pasted text copied a second time is still marked as pasted.

How the figures are worked out

These are heuristics, chosen to point a reader at moments worth a look. None of them, alone or together, is a verdict, and the reader never shows a score.

Replay links

A link is https://theguysaccount.github.io/proof-of-human-writing/verify/#r= followed by the file's exact bytes, compressed with raw DEFLATE (RFC 1951) and encoded as base64url without padding. The editor only offers a link when the result is short enough to survive being pasted into chat and mail apps.

Fingerprint

The fingerprint is the SHA-256 of the file's bytes. Writer and reader see the same one when the file arrived unchanged.

Reference code

The format, the analysis and its tests are in core.js, which runs unchanged in the browser and in Node.js. Use it, or write your own reader: the format is open and the code is MIT licensed.