Why use online text tools?
Reformatting text, encoding a payload, creating a slug: recurring tasks that interrupt your workflow. Instead of opening a local editor or writing a script, our tools handle these operations directly in the browser.
Common use cases:
- Normalize copied text → The case converter transforms ALL CAPS text into clean lowercase
- Prepare an API secret → The Base64 encoder encodes/decodes credentials before pasting into a .env file
- Create clean URLs → The slug generator turns "My Blog Article!" into "my-blog-article"
- Check character limits → The counter validates that your email subject is under 78 characters
How to use the text tools
Step 1: Choose the tool
| Need | Tool to use |
|---|---|
| Change case (lowercase, UPPERCASE) | Case Converter |
| Encode/decode Base64 | Base64 Encoder |
| Create a URL-friendly slug | Slug Generator |
| Count words and characters | Word Counter |
Step 2: Paste and transform
Paste your text in the input area. The tool accepts multiple paragraphs and adapts automatically.
Keyboard shortcuts:
- Mac: ⌘+⏎ to trigger transformation
- Windows/Linux: Ctrl+⏎ to trigger transformation
Step 3: Copy the result
Results appear instantly. Click "Copy" to use them. No data is retained after the transformation.
Tool details
Case Converter
Transform text capitalization in one click:
| Mode | Input | Output |
|---|---|---|
| lowercase | "HELLO World" | "hello world" |
| UPPERCASE | "hello world" | "HELLO WORLD" |
| Title Case | "hello world" | "Hello World" |
| Sentence case | "HELLO. WORLD." | "Hello. World." |
Use case: Normalize text copied from PDFs, emails, or external sources.
Base64 Encoder / Decoder
Convert text to Base64 and back:
| Operation | Input | Output |
|---|---|---|
| Encode | captaindns.com | Y2FwdGFpbmRucy5jb20= |
| Decode | Y2FwdGFpbmRucy5jb20= | captaindns.com |
Common uses:
- Encode credentials for a .env file
- Decode a webhook payload for debugging
- Prepare data for an encoded DNS TXT record
Slug Generator
Create clean slugs from any text:
| Input | Output |
|---|---|
| "My Blog Article!" | my-blog-article |
| "Coffee & Tea: 2024 Guide" | coffee-tea-2024-guide |
| "Summer in Paris" | summer-in-paris |
Transformations applied:
- Remove accents (é → e, ç → c)
- Replace spaces with hyphens
- Convert to lowercase
- Strip special characters
Word and Character Counter
Instant text length analysis:
| Metric | Description |
|---|---|
| Words | Total word count (space-separated) |
| Characters | Total characters (including spaces) |
| Characters (no spaces) | Characters excluding spaces |
| Lines | Number of lines |
Use cases:
- Verify email subject stays under 78 characters
- Validate DNS TXT records don't exceed 255 characters per string
- Estimate reading time (~200 words/minute)
FAQ - Frequently asked questions
Q: Are the text tools free?
A: Yes, 100% free with no signup. No usage limits.
Q: Is my data stored?
A: No. Transformations run in your browser (case converter, counter) or via API without permanent storage (Base64). Your text stays private.
Q: What's the maximum text size?
A: The case converter and counter accept up to 100,000 characters (~15-20 pages). The Base64 encoder supports up to 50KB of data.
Q: How does the slug generator work?
A: The generator applies these transformations in order:
- Remove accents (transliteration)
- Convert to lowercase
- Replace spaces with hyphens
- Strip special characters
- Clean up multiple hyphens
Q: Can I use these tools for DNS records?
A: Yes. The Base64 encoder is useful for encoded TXT records. The counter helps verify the 255-character limit per TXT string (a record can contain multiple strings).
Q: Do keyboard shortcuts work?
A: Yes. ⌘+⏎ (Mac) or Ctrl+⏎ (Windows/Linux) triggers the transformation without leaving the keyboard.
Complementary tools
| Tool | Purpose |
|---|---|
| DNS Lookup | Query DNS records for a domain |
| Propagation Test | Check worldwide DNS propagation |
| SPF Inspector | Validate your SPF record |
| DKIM Inspector | Verify your DKIM signature |
| CSR Parser | Analyze a certificate signing request |
Useful resources
- RFC 4648 - Base64 encoding (official Base64 encoding specification)
- RFC 1035 - DNS TXT records (TXT record limits)
- Unicode Normalization Forms (accent normalization standard)