Models & the .brik format
What the engine loads and how: single-file GGUF straight from Hugging Face, shareable test links, and the .brik streaming format with its in-browser converter.
Run any Hugging Face model
Brimkern reads single-file GGUF directly — the format the Hub already hosts, with no conversion or compilation step. Paste any of these into the field on the home screen (or in the model browser):
Qwen/Qwen3-0.6B-GGUF https://huggingface.co/Qwen/Qwen3-0.6B-GGUF https://huggingface.co/Qwen/Qwen3-0.6B-GGUF/blob/main/Qwen3-0.6B-Q8_0.gguf https://example.com/my-model.gguf
The best quantization is picked for you (Q4_K_M first, then Q4_K_S, Q5, Q8…), and the tokenizer follows the file — nothing to configure. Sharded GGUFs (-00001-of-0000N) and vision projectors (mmproj) are refused with an explicit message rather than half-loaded.
Instant test links
Any model can be turned into a link that loads it directly — handy to share a demo, to file a bug report, or to point a colleague at an exact quantization.
https://brimkern.com/chat?model=Qwen/Qwen3-0.6B-GGUF https://brimkern.com/chat?model=Qwen/Qwen3-0.6B-GGUF&file=Qwen3-0.6B-Q8_0.gguf https://brimkern.com/chat?gguf=https://example.com/model.gguf https://brimkern.com/chat?brik=https://example.com/model.brik
?model= resolves the repository through the Hub API and picks the best loadable file (a .brik wins over a GGUF). ?file= forces one exact quantization. ?gguf= and ?brik= take a direct URL, for models you host yourself.
The .brik format & converter
A .brik is a GGUF re-packaged for the browser: weights already quantized to int4/int8, laid out so each layer is one contiguous HTTP range, with the tokenizer embedded. The practical effect: the model loads by ranges (resumable, partially, genuinely offline afterwards) instead of as one multi-gigabyte download.
You can convert a GGUF yourself, in the browser — the file never leaves your machine: open the converter.
Brimkern — open WebGPU engine, built by Romain Khanoyan. Local AI, WebGPU, on-device engines.