{"slug": "wuffs", "name": "Wuffs", "category": "dev-libs", "category_name": "Libraries and frameworks", "description": "", "recommenders": 4, "commenters": 7, "warners": 0, "score": 4.172, "rising": 0.02, "first": "2025-11-13", "latest": "2026-10-03", "why": "we'll have to replace all parsers with something at least as safe as https://github.com/google/wuffs", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 4, "neutral": 1, "compare": 2, "warn": 0}, "spark": [1, 0, 1, 0, 0, 0, 0, 1, 0, 0, 1, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "we'll have to replace all parsers with something at least as safe as https://github.com/google/wuffs", "kind": "", "icon": true, "domain": null, "github_repo": "github.com/google/wuffs", "official_url": "https://github.com/google/wuffs", "pricing": "", "aliases": ["Wuffs"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 796001873, "item_id": 49750117, "url": "https://news.ycombinator.com/item?id=49750117", "by": "oefrha", "date": "2026-09-18", "stance": "recommend", "quote": "we'll have to replace all parsers with something at least as safe as https://github.com/google/wuffs", "excerpt": "Unsandboxed ImageMagick is known for being a security nightmare even back when PHP ruled the world (not saying sandboxing is a panacea either, it just requires a different and potentially harder exploit to develop a full chain). Difference is it's easier than ever to turn vulnerabilities into full compromises. At some point we'll have to replace all parsers with something at least as safe as https://github.com/google", "context": "", "use_case": "safe file parsing", "switched_from": "", "story": "A heap overflow and SSO misconfiguration to compromise OpenAI internal repos"}, {"id": 776339360, "item_id": 48521210, "url": "https://news.ycombinator.com/item?id=48521210", "by": "nulltype", "date": "2026-06-13", "stance": "recommend", "quote": "wuffs is safer and also often faster", "excerpt": "For the implemented formats, wuffs is safer and also often faster: https://github.com/google/wuffs", "context": "", "use_case": "Safer image format decoding", "switched_from": "", "story": "Twenty One Zero-Days in FFmpeg"}, {"id": 746437312, "item_id": 46652332, "url": "https://news.ycombinator.com/item?id=46652332", "by": "lern_too_spel", "date": "2026-01-16", "stance": "recommend", "quote": "It's existed for years.", "excerpt": "> This may never exist It's existed for years. https://chromium.googlesource.com/chromium/src/+/HEAD/third_party/wuffs/README.chromium Similarly, the JPEG XL decoder Chromium integrated is written in Rust, eliminating large classes of exploitable errors. > Haven't we seen related vulnerabilities? Repeatedly. That's why browser vendors are careful about adding new image decoders, and no, Qubes does not solve the probl", "context": "", "use_case": "", "switched_from": "", "story": "Chromium Has Merged JpegXL"}, {"id": 736604017, "item_id": 46037751, "url": "https://news.ycombinator.com/item?id=46037751", "by": "12_throw_away", "date": "2025-11-24", "stance": "recommend", "quote": "Isn't this exactly the case that wuffs [1] is built for?", "excerpt": "> performant and memory safe decoder (in Rust?). Isn't this exactly the case that wuffs [1] is built for? I had the vague (and, looking into it now, probably incorrect) impression that Google was going to start building all their decoders with that. [1] https://github.com/google/wuffs", "context": "", "use_case": "Safe image decoding", "switched_from": "", "story": "Chrome Jpegxl Issue Reopened"}]}], "caveats": [], "who": [], "tags": [], "use_cases": ["webp decoding", "safe file parsing", "safer image format decoding", "safe image decoding"], "compared": [], "makers": [{"id": 799182832, "item_id": 49948927, "url": "https://news.ycombinator.com/item?id=49948927", "by": "nigeltao", "date": "2026-10-03", "stance": "recommend", "quote": "Wuffs author here.", "excerpt": "Wuffs author here. We got a pull request (https://github.com/google/wuffs/pull/168) in February to add lossy WebP support. Lossless WebP (which in some sense is an entirely different format, just reusing the WebP \"brand\") has had a Wuffs implementation for a couple of years now. Anyway, the PR included SIMD acceleration and performance was on par with libwebp (C code). The PR's code was, as far as I could tell, somew", "context": "", "use_case": "image decoding library", "switched_from": "", "story": "Memory-Safe WebP Decoding"}], "threads": [{"url": "https://news.ycombinator.com/item?id=49941641", "title": "Memory-Safe WebP Decoding", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49749656", "title": "A heap overflow and SSO misconfiguration to compromise OpenAI internal repos", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49437946", "title": "Firefox 157 will include JPEG XL by default on all platforms", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48510046", "title": "Twenty One Zero-Days in FFmpeg", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46597927", "title": "Chromium Has Merged JpegXL", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46033330", "title": "Chrome Jpegxl Issue Reopened", "mentions": 1}], "sentiment_by_month": {"2025-11": {"compare": 1, "recommend": 1}, "2025-12": {}, "2026-01": {"recommend": 1}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {}, "2026-06": {"recommend": 1}, "2026-07": {}, "2026-08": {"neutral": 1}, "2026-09": {"recommend": 1}, "2026-10": {"compare": 1}}, "quotes": [{"id": 799129088, "item_id": 49945568, "url": "https://news.ycombinator.com/item?id=49945568", "by": "omoikane", "date": "2026-10-03", "stance": "compare", "quote": "that would be another implementation worth comparing since it shares the same goals of safety and speed.", "excerpt": "I am not sure what's the current status of Wuffs-based WebP decoder, but that would be another implementation worth comparing since it shares the same goals of safety and speed. https://github.com/google/wuffs/tree/main/std/webp", "context": "", "use_case": "WebP decoding", "switched_from": "", "story": "Memory-Safe WebP Decoding"}, {"id": 796001873, "item_id": 49750117, "url": "https://news.ycombinator.com/item?id=49750117", "by": "oefrha", "date": "2026-09-18", "stance": "recommend", "quote": "we'll have to replace all parsers with something at least as safe as https://github.com/google/wuffs", "excerpt": "Unsandboxed ImageMagick is known for being a security nightmare even back when PHP ruled the world (not saying sandboxing is a panacea either, it just requires a different and potentially harder exploit to develop a full chain). Difference is it's easier than ever to turn vulnerabilities into full compromises. At some point we'll have to replace all parsers with something at least as safe as https://github.com/google", "context": "", "use_case": "safe file parsing", "switched_from": "", "story": "A heap overflow and SSO misconfiguration to compromise OpenAI internal repos"}, {"id": 791204544, "item_id": 49450284, "url": "https://news.ycombinator.com/item?id=49450284", "by": "yboris", "date": "2026-08-26", "stance": "neutral", "quote": "TIL: wuffs - Wrangling Untrusted File Formats Safely", "excerpt": "TIL: wuffs - Wrangling Untrusted File Formats Safely https://github.com/google/wuffs", "context": "", "use_case": "", "switched_from": "", "story": "Firefox 157 will include JPEG XL by default on all platforms"}, {"id": 776339360, "item_id": 48521210, "url": "https://news.ycombinator.com/item?id=48521210", "by": "nulltype", "date": "2026-06-13", "stance": "recommend", "quote": "wuffs is safer and also often faster", "excerpt": "For the implemented formats, wuffs is safer and also often faster: https://github.com/google/wuffs", "context": "", "use_case": "Safer image format decoding", "switched_from": "", "story": "Twenty One Zero-Days in FFmpeg"}, {"id": 746437312, "item_id": 46652332, "url": "https://news.ycombinator.com/item?id=46652332", "by": "lern_too_spel", "date": "2026-01-16", "stance": "recommend", "quote": "It's existed for years.", "excerpt": "> This may never exist It's existed for years. https://chromium.googlesource.com/chromium/src/+/HEAD/third_party/wuffs/README.chromium Similarly, the JPEG XL decoder Chromium integrated is written in Rust, eliminating large classes of exploitable errors. > Haven't we seen related vulnerabilities? Repeatedly. That's why browser vendors are careful about adding new image decoders, and no, Qubes does not solve the probl", "context": "", "use_case": "", "switched_from": "", "story": "Chromium Has Merged JpegXL"}, {"id": 736604017, "item_id": 46037751, "url": "https://news.ycombinator.com/item?id=46037751", "by": "12_throw_away", "date": "2025-11-24", "stance": "recommend", "quote": "Isn't this exactly the case that wuffs [1] is built for?", "excerpt": "> performant and memory safe decoder (in Rust?). Isn't this exactly the case that wuffs [1] is built for? I had the vague (and, looking into it now, probably incorrect) impression that Google was going to start building all their decoders with that. [1] https://github.com/google/wuffs", "context": "", "use_case": "Safe image decoding", "switched_from": "", "story": "Chrome Jpegxl Issue Reopened"}, {"id": 734723088, "item_id": 45920193, "url": "https://news.ycombinator.com/item?id=45920193", "by": "littlestymaar", "date": "2025-11-13", "stance": "compare", "quote": "isn't Wuffs[1] (also made by Google) an even better fit for this particular use-case?", "excerpt": "> Chromium: Parsers for PNG, JSON, and web fonts have been replaced with memory-safe implementations in Rust, making it easier for Chromium engineers to deal with data from the web I find this surprising, isn't Wuffs[1] (also made by Google) an even better fit for this particular use-case? (It has compile-time spatial memory safety, where Rust has compile-time temporal safety but runtime spatial safety, with bound ch", "context": "", "use_case": "", "switched_from": "", "story": "Rust in Android: move fast and fix things"}]}