Viktor.comAn AI coworker that actually does the work
Promoted
Sora Type
Client-side font inspector, built on Vercel
7 followers
Client-side font inspector, built on Vercel
7 followers
Sora Type inspects fonts entirely in your browser — drop OTF/TTF/WOFF/WOFF2 for metadata, glyphs, OpenType features, variable axes, and language support. No upload. Unlike tools that only check character coverage, language reports use real HarfBuzz shaping (WASM), so misplaced marks show up. Compare two fonts with waterfall, glyph overlay, and pairing diagnostics. Built on Next.js + Vercel. Fonts never leave your device (PDF export is the only server hop).
A wishlist item from me: let me save comparison sessions and share them with a short link, so I can send a designer "here's why Font A clashes with Font B at 14px" without us both having to re-upload the same files. Right now comparisons feel a bit lost once I close the tab.
@mirayj8ur Thank you for the suggestion! I've noted this down — saving comparison sessions and sharing them via a short link is a really solid idea, especially for handing off work to a designer. I'll look into adding it in an upcoming release. Really appreciate you taking the time to share this and for following the project!
@mirayj8ur Just shipped it — you can now save and share Compare sessions with a link, no re-uploading needed. Fonts stay private by default; they're only uploaded if you explicitly hit "Create share link," and shared sessions auto-delete after 10 days of no access. Thanks for the suggestion, it made the product better!
Dropped in a WOFF2 and the OpenType feature breakdown popped up instantly, which is way faster than firing up FontForge. The HarfBuzz shaping report caught a mark placement issue I had missed in a Bengali test string, genuinely useful.
@dorukkzltajeny Awesome to hear — glad the feature breakdown gave you an instant read without needing to fire up FontForge. And catching that mark placement issue in your Bengali test string is exactly the kind of thing the HarfBuzz shaping report is meant to surface — those complex-script positioning bugs are easy to miss with a basic glyph/coverage check. Thanks so much for putting it through a real-world test case and sharing the results!
the harfbuzz shaping preview is genuinely useful, way more reliable than the basic coverage check i was using before
@masal1428947 Really glad the HarfBuzz shaping preview is proving useful for you! That was exactly the goal — basic coverage checks can miss a lot (ligatures, contextual substitutions, mark positioning, etc.), so it's great to hear it's giving you more reliable results in practice. Thanks for the kind words and for trying it out!
Running HarfBuzz in WASM to surface actual shaping errors in the browser is the kind of quiet engineering choice that makes this stand out, and keeping the comparison tooling local-first is a nice bonus.
@mtoreli24044 Thanks — glad that landed. HarfBuzz-in-WASM is there so language support isn’t just cmap coverage; we can check real GPOS mark positioning in the browser. And local-first isn’t a side effect for us: fonts stay on-device unless someone explicitly shares a session later.
Today sora type live on Microsoft Edge: https://microsoftedge.microsoft.com/addons/detail/ldcjechdgfjlkkcocjncfonnbefllobl