KBAR Compression

Baudot-safe text compressor with operator & admin tools

WARNING! Compression is NOT encryption!

Message

Paste or type US‑TTY Baudot text (letters, digits & basic punctuation)
Original 0
After compression 0
% of space savings 0.0%
Original: 0 chars • After compression: 0 chars • Savings: 0.0%
Operational note: This tool is designed for compression only. It does not hide content or provide cryptographic security. Treat compressed messages exactly like original clear text for handling, classification, and transmission rules.

Dictionary & preset status

View details of the active compression dictionary

Active dictionary: Tactical (built‑in)

Description:

Entries: 0

Token scheme: )A, )B, )C, …, )Z, )2–)7, then double‑letters like )AA, )AB, … as needed (no hard cap).

Higher‑ranked phrases get earlier token slots. Longer phrases are replaced first to avoid partial overlaps.

Stage 2 (optional): run‑length encoding of repeated characters using patterns like 'A5 ⇒ AAAAA. Only runs that actually save characters are encoded.

To tune compression, use the Admin tab to add high‑frequency phrases from your traffic.

Admin dictionary editor

Password protected • For supervisors / maintainers only

Current password (per design spec) is SubmarinesOnce. You can change this in the source file if needed before distributing.

Help & standard operating guidance

Quick reference for operators and admins
  1. Input format: paste or type Baudot‑compatible plain‑text using uppercase letters, digits, space, and basic punctuation , ! " / ( ) ' .. The tool will internally normalise everything to uppercase.
  2. Compression pipeline:
    • Stage 1 — dictionary substitution using tokens )A…)7 and longer sequences like )AA as needed.
    • Stage 2 — optional run‑length encoding of long character runs (Baudot‑safe).
    • Both stages are fully reversible as long as the same dictionary file is available.
  3. Transmission formatting: compressed output is automatically wrapped at 69 characters per line with no blank spacer lines. Paragraph breaks are preserved via hidden markers and restored on decompression.
  4. Decompression: ensure the receiving system is using the same dictionary preset or imported .kbar file. Decompression runs Stage 2 in reverse first, then dictionary expansion.
  5. Dictionary presets: this build ships with example presets:
    • Tactical — common tactical and reporting phrases.
    • Logistics — supply, movement, and support terminology.
    • Minimal — a very small example dictionary for test traffic.
    • NAVADMIN example — built from the Cycle 118 NAVADMIN posted below for training.
    You can fully replace these with your own phrases in the Admin tab.
  6. .kbar file format: a single JSON object containing a dictionary name, version, and an array of entries with phrase, rank, and enabled fields. It is human‑readable and can be archived with SOPs.
  7. Security warning: again, this system provides compression only. It does not protect confidentiality. If your traffic requires confidentiality, apply approved encryption on top of any compressed text.
  8. Offline use: the entire application runs locally in your browser. You can keep this HTML file on a USB stick or local drive. No network access is required.