changelog.

What's shipped, when. New tools roughly every 1-2 weeks.

↓ RSS Latest first
v1.7.12026-07-30

CHANGED

  • Renamed /erase/ to /watermark-remover/ for clearer positioning and SEO match. Old URL 301-redirects.
v1.7.02026-07-30

NEW — 15 tools shipped

  • base — number base + IPv4 converter
  • barcode — generator + decoder (Code128, EAN, UPC, etc.)
  • blur — blur / pixelate / solid-box redaction
  • cron — parser + builder + next 10 fire times
  • csv — CSV toolkit + JSON/SQL/MD conversion
  • diff — text + JSON diff viewer
  • emoji — picker + kaomoji + Unicode inspector
  • fake — dev seed data generator
  • lorem — Lorem Ipsum with 6 variants
  • pdf-extract — extract images from PDF
  • sign — signature maker (draw + type)
  • tagger — AI image tagger via MobileNet
  • text — sort, dedupe, freq utility
  • units — 10-category unit converter
  • url — parser + UTM builder
v1.6.12026-07-30

SECURITY

  • SRI hash added to dynamically-loaded ONNX runtime in watermark-remover AI mode (CSO finding #4 closed).
v1.6.02026-07-30

NEW

  • random — string / token generator (CSPRNG, hex/base64/custom, bulk)
  • watermark-remover — Fast + AI (LaMa) inpainting modes
v1.5.x2026-07-29 → 30

NEW

  • Cloudflare Pages migration (from Hostinger origin). ~200ms → ~30ms TTFB globally.
  • Static content pages coming.

SECURITY

  • JWT XSS finding closed via escapeHtml() on claim values.
  • Markdown tool refuses to render when DOMPurify blocked (no unsafe fallback).
  • SRI hashes added to 21 CDN <script> tags.
v1.5.02026-07-29

NEW

  • pipeline — visual recipe builder. Chain tools, save recipes, one-click rerun.
v1.4.02026-07-29

NEW

  • PWA share target — mobile "share to nap tools" routes into the right tool.
  • File Handling API — right-click images on desktop → open in nap tools.
  • /open/ router page for share + file-handler intake.
  • 10 tools wired to receive files via napPipe.
v1.3.x2026-07-29

NEW

  • svg — SVGO in browser
  • icons — icon set generator (PWA/iOS/Android)
  • annotate — screenshot annotator with blur/redact
v1.2.x2026-07-28

NEW

  • Recipes engine — chain tools, save, run
  • QR decoder mode added to qr
  • Command palette (Cmd+K / Ctrl+K) — fuzzy-search any tool
  • Pinned tools strip on hub
  • Settings modal (⚙) — theme, analytics toggle, install prompt
  • PWA install banner after 2nd visit
v1.1.x2026-07-25

NEW

  • QR generator design pass — module shapes, gradient fills, frame + caption
  • 15 new tools: contrast · gradient · jwt · base64 · password · timestamp · uuid · hash · markdown · regex · case + earlier batch
v1.0.02026-05-16

LAUNCH

  • Initial release: 13 tools (image + PDF + JSON). Product Hunt launch.

How releases work

Every release is versioned, dated, and shipped as a single Cloudflare Pages deploy. There is no staging environment other than a local dev server — changes go straight from repo to production once the smoke tests pass. That keeps the loop tight and forces every commit to be small enough to ship on its own. Two things follow: (1) if you spot a regression, the offending change is almost always the most recent one, and (2) rollbacks take about a minute.

Version policy

Major version bumps mean a real shift — a new architecture (v1.5 shipped the visual recipe builder, v1.4 shipped the PWA share target), a rename that breaks external links (v1.7.1 renamed /erase/ to /watermark-remover/ — the old URL still 301-redirects), or a batch of new tools that expands the site's scope by more than 10%. Minor versions are ordinary feature and tool additions. Patch versions fix bugs, security findings, or perf regressions.

The service worker's VERSION constant always matches the deploy version. If you're on an installed PWA and a tool starts behaving oddly, opening Settings → Clear PWA cache forces the fresh version to install — most odd behavior traces back to a stale service worker holding onto an old asset.

Roadmap signals

The roadmap is driven by three signals, in order of weight: (1) what people actually reach for on the hub (which is why squish and cutout are the most-maintained tools), (2) obvious functional gaps that would let existing users chain more work through pipeline, (3) SEO gaps — tools that would rank if they existed and match the site's client-side-only mandate. Feature requests come in via napdesigns.com or @nap.codes on Instagram; ideas that would require a server backend are declined by default — this whole project exists because I wanted a set of tools that don't have one.

Subscribe to changes

An RSS feed is generated on every release with the same version, date, and summary you see here. Add it to any RSS reader — Feedly, NetNewsWire, Inoreader, Reeder, Miniflux — and you'll see new tool drops and security fixes the day they ship. There is no email newsletter and no push notification; the feed is the one channel.

Something looks wrong on this changelog? DM @nap.codes on Instagram or via napdesigns.com.