Local Notebook Output Clearer
Clear stored code-cell outputs and execution counters from a small local ipynb while preserving every other original JSON byte.
Loading tool…
How to use Local Notebook Output Clearer
Create a separate notebook copy without stored code execution results. A bounded lexical index finds only code-cell outputs and execution_count values; replacing those spans preserves unrelated metadata numbers, source code, whitespace, attachments and widget state exactly. No notebook code or rich output is rendered or executed.
- Choose a small supported ipynb or load the generated original example.
- Run the local clear operation and review exact field/byte ranges, removed record counts and input/output hashes.
- Download the separate notebook or evidence, then review retained source and metadata before sharing or opening it elsewhere.
Good to know
- One fatal-decoded UTF-8 file of at most 1 MiB, 20,000 JSON values, 40 levels, 200 cells and 1,000 stored code-output records. One initial UTF-8 BOM is preserved. Duplicate decoded object keys, malformed JSON and unpaired Unicode surrogates are refused.
- Supports selected nbformat 4.0–4.5 fields. Root/cell metadata must be objects, cells must be code/markdown/raw and source must be a string or string array. Minor 5 requires unique valid cell IDs; any present IDs are checked. Selected version/counter numbers are validated from exact original numeric tokens; code counters are null or integers from 0 through 1,000,000,000.
- Only nonempty code outputs values become [] and nonnull code execution_count values become null. Every unrelated original UTF-8 byte remains unchanged, including large metadata integer spellings, whitespace and embedded strings. This is a selected-field operation, not full notebook schema validation or a repair tool.
- Source code, markdown/raw content, attachments, cell/root metadata and widget state can retain private data or executable content for another application. Clearing outputs is not anonymization, sanitization, malware removal, trust signing or safe execution. Review all remaining content in a trusted environment before sharing.
- Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.
Common questions
Does the cleaned notebook remove all secrets or become safe to execute?
No. Secrets and active content can remain in source, metadata, attachments or widget state, which this operation deliberately preserves. The output has fewer stored execution results; it is not anonymous, trusted or certified safe to run.
Is this input sent to a server?
No. The application processes this input inside your browser tab and does not save it to persistent storage.
Keep going with related tools
All files →JSON Viewer
Inspect a JSON document as a safe path, type, and value tree without executing its contents.
DataStructured Data Redaction Preview
Replace or remove explicitly selected JSON Pointer fields and show a transparent local change report.
FilesFile Hash Verifier
Hash exact local file bytes with SHA-2 and optionally compare a supplied expected digest.