Operational Limits and Performance Budgets

File Size Limits & Operating Modes

To guarantee responsive interactive editing and eliminate browser out-of-memory crashes, Bitpeek defines clear operational bounds:

• Browser Interactive Edit Limit: 256 KiB maximum per document. This ensures instantaneous keystroke feedback, synchronous bit manipulation, and full transactional undo/redo history.
• Browser Read-Only Target: 64 MiB for viewing, streaming search, string scanning, structure header inspection, and progressive hashing.
• CLI & MCP Streaming: Files up to 512 MiB are processed using bounded 1 MiB chunk streams, keeping heap consumption below 128 MiB.

Result Caps & Pagination

Operations that could produce unbounded outputs enforce explicit pagination:

• Pattern Searches: Capped at 1,000 matches per page with a nextCursor offset to continue scanning.
• String Extraction: Capped at 1,000 strings per page with preview length limits.
• Structure Nodes: Capped at 10,000 tree nodes per document with a maximum nesting depth of 32.
• Custom Schemas: Schemas are capped at 256 KiB file size and 1,000 field definitions.

Web Build Size Budgets

Bitpeek strictly monitors bundle size on every build:

• Homepage HTML: ≤ 6 KiB gzip (measured: ~3.2 KiB).
• Initial Application JavaScript: ≤ 110 KiB gzip (measured: ~83.2 KiB).
• Application CSS: ≤ 7 KiB gzip (measured: ~5.9 KiB).
• Total Initial Transfer: ≤ 150 KiB gzip (measured: ~95.3 KiB).

Local processing and privacy

The Limits & budgets workflow opens the same Bitpeek browser workspace. Selected file bytes, file names, pasted input, searches, edits, hashes, and comparison data are processed in local browser memory and are not sent to a Bitpeek server.

The static guide itself can be read without opening a file or creating an account.

Frequently asked questions