Pimp My IDE / Garage dispatch
Back to garage
September 28, 2026 | WebGPU / fonts / local tools

A font matcher gives you suspects. You still need an identification.

GPU-font can rank typeface candidates inside the browser without uploading the crop. That is a useful first pass. The shipping decision still needs glyph comparison, a real font source, and a license check.

The take. Local inference changes where the image travels. It does not turn a ranked guess into font provenance. Use the speed to build a better lineup, not a faster false certainty.
Build an inspection cardTry gpu-font

The crop can stay in the garage.

GPU-font runs on the user's device through WebGPU or a CPU fallback. Its project page says the image is not uploaded. The matcher splits a crop into as many as three grayscale windows. Each window is at most 128 by 48 pixels. A small neural network scores fonts for each window, then averages the scores into a ranking.[1]

The published package is real. The garage installed version 0.2.0 and imported its three public exports on September 28. The repository documents browser and Node use, custom local catalogs, and an MIT license.[2]

A local result can protect the crop. It cannot certify the font.

A ranking needs a boundary.

The project's reported accuracy is measured on rendered crops of Google Fonts families using text that the model did not train on. It reports the right family first 73 percent of the time and in the top five 92 percent of the time. Those figures come from the project. They do not describe every photograph, logo, outline, compressed screenshot, or commercial face.[2]

The project says photos, blur, perspective, texture, short samples, mixed fonts, and look-alike families can reduce match quality. The correct response is not to hide the lower confidence. Keep several candidates and find the glyphs that separate them.

WebGPU needs a fallback lane.

MDN marks WebGPU as limited availability and says it requires a secure context. It supports general GPU computation as well as graphics, which makes in-browser inference possible. A public tool still needs feature detection and a CPU route when the browser cannot supply a WebGPU device.[3]

That fallback is part of the product, not an apology. A matcher that explains its slower path is more useful than a glossy upload box that fails on an unsupported machine.

Finish with provenance.

Compare a long string, numerals, punctuation, and a few distinctive glyphs. Find the font through its foundry, an official catalog, or the repository that distributes it. Read the license for the actual file and use case. The gpu-font site makes the same boundary explicit: a match is not a license.[1]

The useful output is a short comparison record. It names the crop conditions, candidate, separating glyphs, file source, and license status. That record can survive after the screenshot and browser tab disappear.

Interactive makeover / optical inspection

Font identity lineup

Traditional purpose replaced: paste a screenshot into a black box and copy the first name. Better version: record crop conditions, keep a candidate visible, close four manual checks, and copy an honest comparison card.

Put the candidate under the inspection light

This teaching bench does not run the gpu-font model. It prepares the manual checks that follow a ranked result.

Quiet rivers
Clean render
Crop condition
Ranked candidate
Manual proof clamps
0 of 4 manual proof clamps are closed. Candidate only.
Copyable comparison card

Carry the uncertainty with the candidate

The card records what you inspected. It never changes the candidate into a confirmed identity.

What this control proves. It keeps crop condition, sample, candidate, and four manual checks in one handoff. It does not identify a font, run a model, verify a file, or grant a license.

Sources and limits

Open the source log
  1. gpu-font project site, read September 28, 2026. It describes the local WebGPU and CPU paths, crop windows, ranking method, input limitations, custom catalogs, alternatives, and license boundary.
  2. dy/gpu-font repository, release 0.2.0 inspected September 28, 2026. The repository documents its package, catalogs, benchmark figures, source code, training material, and MIT license. The garage installed package version 0.2.0 with scripts disabled and imported catalogs, createEncoder, and createMatcher.
  3. MDN, "WebGPU API", read September 28, 2026. MDN documents general GPU computation, secure-context requirements, feature detection, device access, and current limited availability.
  4. Hacker News discussion 49875638, item title and destination verified through the Hacker News API on September 28, 2026. The thread is a discovery route, not evidence for the project's claims.

Source boundary. Accuracy, privacy behavior, catalog size, and implementation details come from the project publisher and repository. The package import proves that version 0.2.0 was available and importable in one Node environment. It does not reproduce the model benchmark or audit browser network traffic. MDN documents WebGPU, not gpu-font quality.