Join the conversation

Join the community of Machine Learners and AI enthusiasts.

Sign Up
maglun 
posted an update 8 days ago
Post
2945
Inspect model quantization in the browser, without download

Curious how models on Hugging Face spend their "bit budget"? A few days ago I shared the first version of a little tool I built out of my own curiosity (and for fun). Since then, thanks in large part to great feedback from people here, a lot has changed.

New in the last few days:
- GGUF support - handy with all the new great GGUF quants
- Decode for AWQ, GPTQ, NF4, mxfp4 packed experts, packed-int32, and additive-codebook formats
- Improved comparison view for diffing two quants of the same model
- Built-in anonymous report-issue button connecting a report to specific model
- plus many small fixes

After my first post I got great feedback from several community members, and some issues were fixed within hours. I'm planning an acknowledgments section on the site, and when you report an issue you get a receipt ID you can keep to claim credit later. (reports are anonymous by design; I store no identity, so the receipt hash works like a bearer token for your find)

It's still very much a side project I hope others find useful. Explore any HF model in the browser without downloading it, the webpage reads from the safetensors header via a range request, and only tensors you click stream, and large ones are sampled, not downloaded in full. And there is a report button right in the tool when things don’t look right.

Feedback very welcome, especially models that break it :) Or ideas on what is missing.

https://tensorlens.dev
(screenshot attached from viewing one of Unsloth's GGUF quants)

The report-issue receipt is a strong design choice: it makes anonymous feedback recoverable without collecting identity. For quant inspection, exposing parsed architecture and quantization metadata beside the sampled tensor view could make cross-format discrepancies easier to diagnose. Which format has produced the hardest edge case so far?

·

Thanks, that's right, I wanted reports recoverable without an account or storing any identity, so a bearer-style hash over the find was the natural fit. Glad it read that way.

Agreed on surfacing parsed architecture + quant metadata beside the tensor view, that's the direction I want to take it, and it's most valuable in the comparison mode where cross-format discrepancies bite. Right now clicking a tensor gives you the sampled distribution plus dtype/bits/group-size; adding the full parsed quant metadata (format, block layout, scale placement) next to it is what turns a diff from "these two numbers differ" into "here's why" 😄

Hardest edge case so far, I would say GGUF IQ-quants (IQ1_S / IQ2_XXS, etc), the codebook/lookup block structures are tricky to get right. Or NF4 with the nested/double quantization (quantized absmax). 😅

If you hit a format that you think renders wrong, the report button is right there. Those reports genuinely help, and I especially welcome the hard ones. 🙏

This comment has been hidden (marked as Off-Topic)