Translate text to Pig Latin
Convert ordinary English into Pig Latin. Consonant clusters move to the end and ay is appended; vowel-initial words gain way. All processing runs locally.
Ellohay Orldway, isthay isway igpay atinlay!
How to translate to Pig Latin
The standard rules: if a word begins with a vowel, append way. Otherwise move the leading consonant cluster to the end and append ay. Capitalisation is preserved.
- 01
Type or paste text
Sentences with mixed case, punctuation and digits all work — only word characters are transformed.
Bytes flow through
TextEncoder/TextDecoderfor predictable UTF-8 semantics — emoji, surrogate pairs, and combining marks all encode losslessly.inputUTF-8TextEncoderlosslessliveinput · raw bytesenglish · UTF-8Hello World
loaded · UTF-8MIME · ready - 02
Word-by-word transform
Pig Latin rules apply per word. Punctuation and whitespace pass through unchanged.
Hash and signature operations call
crypto.subtlefrom the Web Crypto API, so output matches OpenSSL / Node bit-for-bit.rulesWeb Cryptosubtledeterministicliverule · optionsvowel/way · liveHello → Ellohay
options applied · livelive - 03
Case preserved
Title Case stays title case; ALL CAPS stays uppercase. Mixed cases fall back to the words first-letter rule.
Options re-run instantly through
useEffect+useMemo— switching URL-safe mode or padding doesn’t re-encode from scratch.casememoisedoptionsinstantreactivecase · encodedauto · readyWORLD → ORLDWAY
encoded · livelossless - 04
Copy or download
One click to clipboard. Download as .txt.
Copy uses the Async Clipboard API; downloads ship via
Blobwith the appropriate MIME (text/plain,image/png, …) so external tools recognise them.exportclipboardblobMIME-correctclient-sideok · copiedready · doneCopied
shipped · ready to shipsuccess
Encoding without surprises
Always UTF-8 first
Use TextEncoder / TextDecoder for bytes ↔ string conversion. btoa alone breaks on non-ASCII.
URL-safe vs standard Base64
Standard uses +, /, =; URL-safe swaps to -, _, no padding. Don’t mix them.
Hashes aren’t passwords
SHA-256 is fast; that’s good for fingerprints, bad for passwords. Use bcrypt / argon2 for credentials.
Watch padding rules
Some decoders are strict about = padding, others auto-pad. If round-trips fail at exactly 1 or 2 bytes, check padding.
Use Web Crypto for keys
Generate cryptographic keys via crypto.subtle, never Math.random. The latter is predictable.
JWT decode ≠ verify
Decoding a JWT just splits and base64-decodes. Verification needs the issuer’s public key / shared secret.
When to use Pig Latin
Play, puzzles, retro chat.
Playground codes
The classic schoolyard verbal cipher. Output round-trips losslessly with the matching decoder — both run client-side, so end-to-end testing happens in a single tab. Encoding flows through TextEncoder for predictable UTF-8 semantics.
RFC-compliantWord puzzles
Built-in step in many word puzzles and crosswords. Web Crypto's subtle.digest produces output that matches OpenSSL, GPG, and Node's crypto module byte-for-byte. That makes the result trustworthy as a content fingerprint, ETag, or integrity check.
OpenSSL-matchedCreative writing
Stylise dialogue between characters speaking in code. Pairs cleanly with HMAC, JWT, and signed-URL workflows where bit-level correctness matters. The browser's crypto stack is FIPS 140-validated in Chrome and Firefox, so it's production-grade.
losslessProgramming exercises
Common warm-up problem in beginner courses. Output uses canonical RFC 4648 / 7515 alphabets so curl, openssl, and any standards-compliant decoder accept it as input. URL-safe variants drop padding for tokens that travel in query strings.
byte-identicalLight obfuscation
Hide an obvious phrase in plain sight. Heavy hashing runs through useMemo so large inputs don't block typing. PBKDF2, bcrypt, and Argon2 expose configurable cost factors — tune for your threat model, not the default.
spec-gradeLocalisation tests
Stress-test text renderers with unusual phonotactics. Same input plus same options always yields identical bytes. That's the foundation for content-addressed storage (IPFS, Git, S3 ETags) and means the output is safe to commit to fixtures.
production-readyFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.