wikistego
plain or encrypted text in mediawiki pages
local · no tracking
0 chars · +0 B on page
invisible payload — ready to paste
0 payload bytes  ·  0 zwc chars  ·  +0 KB
→ edit source, not the visual editor
→ use place — it returns the whole patched page
manual copy
or drop a .wiki / .txt file here
fetches that page's wikitext straight from the wiki
what does this actually do?

It turns a message into zero-width Unicode characters and wraps them in a checksummed frame. Pasted into wikitext, the page renders exactly as before — no visible text, no visible diff.

which alphabet does it use?

Two symbols carry the bits, one acts as a boundary marker:

U+200BZERO WIDTH SPACEbit 0
U+200CZERO WIDTH NON-JOINERbit 1
U+2060WORD JOINERframe delimiter

Bits are written most-significant first, 8 symbols per byte. Two alternate pairs (U+200B/U+200D and U+200C/U+200D) are selectable; the decoder detects which one was used. The marker is outside the alphabet, so it can never be mistaken for payload.

source or rendered text?

Always the wikitext source. The rendered page is post-parser output — boundary characters may already be gone, and copying it can add or lose whitespace. Any single shifted character breaks every bit after it. Use edit source or ?action=raw.

how does page import work?

Paste a full page URL and the decoder works out that wiki's api.php, then asks the API for the wikitext and fills the box. If the wiki blocks cross-origin requests, open the page's ?action=raw and paste it by hand. The request goes straight from your browser to the wiki you named — no third party, no relay.

how much does it add to the page?

1 byte of message = 8 zero-width characters = 24 bytes of page. A 60-character message is about 2 KB. Page history shows the growth even though the diff looks empty.

is it really hidden?

From readers, yes. From anyone who opens the raw wikitext, no. Encryption is the only thing that makes the content secret; without it, anyone who knows the format can decode the message.

what does the password protect?

Everything. PBKDF2-SHA256 at 600,000 iterations derives an AES-256-GCM key; the salt, IV and tag travel with the payload. No password, no recovery — and a typo cannot be detected, which is why encode asks twice.

will it survive on a wiki I don't control?

Maybe. Edit filters and cleanup bots delete invisible characters. Test with a short message in User:you/sandbox, confirm it survives ?action=raw and a VisualEditor no-op save, and keep a local copy of the plaintext.

U+2060 · WSG2 · crc32 · PBKDF2 600k · AES-256-GCM nothing stored · imports go straight to the wiki