cryptowave

Hey IH,

I launched CryptoWave (cryptowaveapp.com) less than a week ago

and wanted to share what I built and what I've learned so far.

What it is

33 browser-based tools — AES/RSA encryption, SHA-256/Bcrypt

hashing, audio/video conversion, PDF merge/split, QR codes,

image compression. Everything runs client-side. No uploads,

no accounts, no cookies.

I built it because I kept using random online tools to encrypt

files or convert audio, but never felt confident about where

my data was going. So I made one where it never leaves the device.

Tech stack

Vanilla HTML/CSS/JS — no framework. FFmpeg.wasm for media

processing. pdf-lib for PDF tools. Deployed on Cloudflare Pages

for free.

What I did this week

Mostly SEO groundwork:

- Fixed canonical URL mismatches (Cloudflare strips .html,

my canonical tags didn't — caused redirect errors in GSC)

- Added HowTo schema + expanded FAQs on 10 pages

- Split hash.html into dedicated sha256.html and bcrypt.html

pages so each algorithm can rank independently

- Added a Related Tools section across all pages for

internal linking

Numbers after 1 week

- 15 real visitors (GA4)

- Cloudflare shows ~500 "visits" but most are bots/crawlers

- 3 tool_used events tracked

- 0 signups (no accounts to sign up for)

What I'm figuring out

Getting initial traction without a built-in audience is harder

than building the thing. If anyone has shipped something similar

and found a channel that actually worked early on, I'd love to hear it.

Happy to answer any questions about the FFmpeg.wasm integration

or the Web Crypto API — those had the most gotchas.

CryptoWave — 33+ free browser-based crypto, media, and utility tools. No uploads, no servers, no accounts.

What I shipped today

This week I focused entirely on SEO fixes and site polish. No new features — just making what already exists work better for search engines and users.

1. Fixed Google Search Console redirect errors

Cloudflare Pages automatically strips .html from URLs (e.g. /pages/audio.html → /pages/audio). My canonical tags still had .html in them, so Google was flagging every page as a "redirect error." Batch-replaced all 35 canonical URLs across the site to remove the extension. Also updated sitemap.xml to match.

2. Split hash.html into dedicated pages

hash.html was a single page covering SHA-256, MD5, SHA-512, HMAC, and Bcrypt — five algorithms in one URL. Split SHA/MD5 and Bcrypt into their own dedicated pages (sha256.html, bcrypt.html), each with their own title, meta description, canonical URL, and JSON-LD schema. This gives each algorithm a chance to rank independently.

3. Added HowTo schema + expanded FAQs

Added JSON-LD HowTo schema (step-by-step instructions) and expanded FAQs from 3 to 6+ items on 10 tool pages. These are the two content formats Google most commonly surfaces as featured snippets.

4. Added Related Tools section

Injected a "Related Tools" section before the footer on every page via a single JS function. No changes needed to individual HTML files — just one RELATED map in utils.js. Internal linking helps Google understand site structure and passes PageRank between pages.

5. Fixed alert text invisible in light mode

Had hardcoded color: #f5dec8 (a light cream) on .alert--info. Fine on dark background, completely invisible on light. Changed to color: var(--text-primary) so it respects the active theme.

6. Updated branding

Replaced the emoji favicon with a proper transparent PNG app icon. Updated the navbar logo to match. Also added og:image for social sharing previews (for Threads/Twitter cards).

Numbers

• Pages with HowTo schema: 10

• Pages with expanded FAQ (6+ Q&A): 10

• Internal links added: ~120 (3–4 per page × 34 pages)

• New dedicated pages: 2 (sha256, bcrypt)

• GSC redirect errors fixed: 9

Quick update on what I shipped over the past few weeks.

---

What is CryptoWave?

Free browser-based developer tools — encryption, hashing,

audio/video conversion, PDF tools, and more. Everything runs

100% client-side. No accounts, no uploads, no servers.

→ cryptowaveapp.com

---

## What's new

6 color themes

Added Ocean, Ocean Light, Forest, and Forest Light on top of

the existing Light and Dark. Small thing but users seem to

notice and appreciate it.

Image to WebP Converter

New tool for batch-converting JPG/PNG images to WebP.

Added it after noticing "jpg to webp" was one of the

search terms bringing people in.

Recently Used Tools

Homepage now shows the last 6 tools you visited.

Speeds up repeat usage without needing accounts or cookies.

Back to Top button

Small QoL improvement — shows up after scrolling,

matches the current theme color.

---

## What I learned

The SEO from FAQ sections (structured data + FAQPage schema)

is starting to show up in Search Console impressions.

Takes time but it's working.

Still figuring out the right content/SEO strategy.

Open to any advice from people who've grown tool sites.

---

What features would you find most useful in a tools site like this?

Hi everyone,

I’m the maker of CryptoWave. Like many of you, I often need to convert an audio file, compress an image, or encrypt some text quickly.

But every time I Googled for these tools, I felt uneasy. Most "free online tools" require you to upload your files to their servers. As a developer, I kept thinking: Why should I send my private data to a server just to run a simple FFmpeg command or a CryptoJS script?

So, I built CryptoWave (https://cryptowaveapp.com/).

The "secret sauce": It runs entirely in your browser.

• Audio/Video: Uses FFmpeg.wasm to process files locally.

• Crypto: AES/RSA/Hash logic stays on your machine.

• No Cookies/Tracking: I wanted it to be as "clean" as possible.

Tech Stack:

• Frontend: Vanilla JS / HTML / CSS (Keep it fast and lightweight!)

• Hosting: Vercel

• Processing: WebAssembly (FFmpeg.wasm)

What's next? I’m planning to add more developer utilities like a JSON formatter and a Regex tester.

I’d love your feedback:

1. Does the UI feel intuitive to you?

2. Are there any specific "server-less" tools you've been looking for but couldn't find?

Thanks for checking it out!

CryptoWave is a browser-based toolkit that lets you perform common crypto and audio tasks without installing anything or sending data to a server.

It includes tools for AES encryption, RSA operations, hashing, encoding, and even audio conversion powered by FFmpeg.wasm — all running entirely in the browser.

One of the interesting aspects of this project is that everything is client-side. It uses the Web Crypto API for cryptographic operations and WebAssembly (FFmpeg.wasm) for media processing, which means your data stays local.

The goal is to make these tools fast, simple, and accessible, especially for developers who just need something quick without switching between multiple services.

It’s also a good example of how far modern browsers can go without a backend.