A browser extension that adds processor context to Geekbench CPU results and comparisons. GeekLens presents processor identity, topology, frequency and memory details, score context, result validity and, where supported by available evidence, instruction-set annotations.
- Supports Geekbench 5, 6 and 7 CPU result and comparison pages.
- Identifies the processor vendor and architecture, cleans up reported names and links exact matches to the Geekbench processor catalogue.
- Presents core, thread and cluster topology, including sourced core-type names when the reported layout can be matched unambiguously.
- Summarises the submitted run's frequency samples as a range and compact distribution.
- Adds memory capacity, configuration and bandwidth details from reported, computed or published data, with sources shown where applicable.
- Shows multi-core scaling and generation-matched Geekbench Browser average scores and deltas.
- Carries Geekbench result-validity information over to comparison pages and explains invalid results.
- Marks identified engineering samples and warns about known reporting problems, such as incorrect L3 totals on affected Ryzen X3D results.
- Adds system and per-workload instruction-set annotations when reliable capability and workload data are available. Unconfirmed mappings are labelled as such.
- Provides separate settings for each data group, badge colours, tooltips and mapping warnings.
Geekbench results contain useful hardware and run metadata, but much of it is terse, split across views or absent from comparison pages. GeekLens presents that information in place without changing the benchmark scores.
Reported, computed and published facts are kept distinct. Published processor and system details come from a reviewed, bundled catalogue and include source links. Ambiguous hardware matches are left unresolved rather than guessed.
- Install from the Chrome Web Store
- Or install manually:
- Download this repository, run
bun install, then runbun run build:chrome - Go to
chrome://extensions/ - Enable "Developer mode"
- Click "Load unpacked" and select the
dist/chromedirectory
- Download this repository, run
- Install from Microsoft Edge Add-ons
- Or install manually:
- Download this repository, run
bun install, then runbun run build:chrome - Go to
edge://extensions/ - Enable "Developer mode"
- Click "Load unpacked" and select the
dist/chromedirectory
- Download this repository, run
- Install from Firefox Add-ons
- Or install manually:
- Download this repository, run
bun install, then runbun run build:firefox - Go to
about:debugging#/runtime/this-firefox - Click "Load Temporary Add-on"
- Select the
manifest.jsonfile in thedist/firefoxdirectory
- Download this repository, run
- Install the extension
- Visit a supported CPU result page (for example, https://browser.geekbench.com/v7/cpu/1248)
- GeekLens adds the available processor and result context to the page
Geekbench 7 instruction data is only available while signed in to Geekbench, including on single-result pages.
Geekbench 5 exposes no instruction-set capability data in the captured result pages or payloads. Processor context remains available, but ISA workload annotations do not.
- Processor and system context is derived from Geekbench result metadata and a bundled catalogue of reviewed hardware facts. Published values retain their source links.
- Geekbench 6 workload mappings are based on the Geekbench 6 benchmark internals documentation.
- Geekbench 7 system instruction sets are read from the result payload. Per-workload mappings remain deliberately limited and carry an amber warning until equivalent benchmark-internals documentation or direct instruction traces are available.
- Geekbench 7 data sources and confidence records the mapping provenance, open questions and evidence requirements.
- Processor catalogue sources records the source hierarchy and maintenance policy for published hardware data.
- Bun 1.3.14 or newer
- Node.js 24.18 or newer
- A modern web browser (currently Chrome or Firefox have been tested)
- Clone this repository
- Install dependencies:
bun install - Development mode:
bun dev
- Build for production:
- For Chrome:
bun run build:chrome - For Firefox:
bun run build:firefox
- For Chrome:
- Run tests:
Other quality checks:
bun testbun run lint bun run format:check bun run check - Create distribution zip files:
- For Chrome:
bun run release:chrome - For Firefox:
bun run release:firefox
- For Chrome:
- Load the extension:
- Chrome:
- Navigate to
chrome://extensions/ - Enable "Developer mode"
- Click "Load unpacked" and select the
dist/chromedirectory
- Navigate to
- Firefox:
- Navigate to
about:debugging#/runtime/this-firefox - Click "Load Temporary Add-on"
- Select
manifest.jsonfile in thedist/firefoxdirectory
- Navigate to
- Chrome:
- This project uses vite-plugin-web-extension for building browser extensions with Vite
- Both builds use Manifest V3. Chromium runs the background as a service worker;
Firefox runs it as an event page, since Firefox does not support
background.service_worker
Open an issue before making a substantial behavioural or data-model change. Corrections to processor data should include a suitable source; see the catalogue source policy above.
This project is licensed under the MIT License - see the LICENSE file for details.
GeekLens is not affiliated with Primate Labs Inc. or Geekbench. All trademarks belong to their respective owners.





