Blog & changelog
Blog & changelog
Long-form notes and changelog entries: engineering rationale, privacy boundaries, and what changed—written to stand alone as useful reading, not only as captions for tool UIs.
2026-06-18
Why RGB vector decomposition needs residuals for strict lossless
RGBV3D vector-v2 stores each pixel as a direction code, a norm proxy, and per-channel residuals. Without the residual layer, quantizing direction and magnitude would be lossy: two different RGB triplets could map to the same vector representation, and decode would invent colors that never existed in the source raster.
Read full article →2026-06-15
Classic vs vector-v2: where we beat PNG and where we lose
Profile 0 (classic) in RGBV3D resembles a PNG mental model: spatial prediction across the raster, then Deflate on the residual stream. Profile 1 (vector-v2) tries to exploit directional coherence in RGB space with a codebook plus exact residuals. Neither profile promises a win on every file.
Read full article →2026-06-12
Browser decode boundaries for .rgbv3d (memory and WASM)
The PracticalKit RGBV3D encoder runs client-side via @rgbv3d/core compiled for the browser. That keeps uploads off our servers but imposes hard ceilings: JavaScript heap limits, WASM linear memory growth, and single-threaded execution on main stream paths.
Read full article →2026-06-10
Block noise triage: why grainy images explode in size
Block-adaptive codecs need a triage step: classify regions as smooth, edge-heavy, or noise-heavy before picking predictors. RGBV3D research calls this noise-aware routing. When triage mis-labels grain as smooth, predictors fail and entropy coding spends bits aggressively. When triage correctly marks noise, the encoder may fall back to classic-like paths—accepting larger files instead of pretending compression.
Read full article →2026-06-08
PNG → .rgbv3d → PNG: a pixel-level verification workflow
Lossless claims require evidence. Our recommended workflow for skeptics and integrators:
Read full article →2026-06-05
.rgbv3dvi multi-frame container: current status and limits
Animated and multi-frame RGB archives need timing metadata, per-frame dimensions, and shared codebooks without breaking lossless guarantees on each frame. The proposed .rgbv3dvi container (documented on /rgbv3d/roadmap/) is experimental—not something you should bulk-deploy today.
Read full article →2026-05-28
Merging PDFs in the browser without uploading to a server
Server-side PDF mergers see your documents. For contracts, medical forms, or unreleased designs, that data path is unacceptable even if the vendor promises encryption. PracticalKit’s PDF merge path uses pdf-lib in-tab: files are read via File API, merged into a new ArrayBuffer, and offered as download.
Read full article →2026-05-22
JSON diff in CI: three real config cases
Configuration drift breaks deployments quietly. Line-based diff on minified JSON is unreadable; key order noise hides real edits. PracticalKit’s JSON diff tool sorts object keys recursively so CI humans see semantic changes.
Read full article →2026-05-18
How we label local-only tools vs API-backed tools
PracticalKit shrunk to twelve flagship tools plus RGBV3D documentation. Each page declares a processing mode in the editorial footer: local, file/media, or third-party API. We removed tools that duplicated the same pattern without unique prose.
Read full article →2026-05-14
Browser-first data handling patterns
Browser-first does not mean “no network.” It means the sensitive transform happens on the user agent unless explicitly outsourced. PracticalKit applies three patterns:
Read full article →2026-05-10
Choosing PNG, WebP, or AVIF for screenshots and archives
PNG remains the interchange lingua franca for lossless RGB with broad tool support. WebP lossless often beats PNG on photographic screenshots but may fail in older print pipelines. AVIF lossless is promising yet inconsistently supported in desktop editors.
Read full article →2026-05-05
Base64 and URL-safe encoding pitfalls
Base64 looks simple until JWTs, data URLs, and form bugs collide. PracticalKit’s encoding tool focuses on common developer footguns:
Read full article →