comparison · LoupeKit vs VisBug
LoupeKit vs VisBug: which one should you install?
VisBug is free, open source, made at Google Chrome Labs, and it is the best answer to a question this extension does not really answer: what if the browser had a design tool in it. Marquee-select anything, nudge it, align it, edit the text, tweak the type, at any device size, on any framework. If you want to *change* a rendered page, install it - nothing here replaces it.
Changing a rendered page: VisBug. Reading one: LoupeKit. VisBug is free and open source, so install it either way.
VisBug
Free · open source · Chromium, Firefox and Safari
Design-tool interactions and hotkeys applied to a live page. Move, align, measure distances, edit text in place, inspect spacing and accessibility, adjust type, and see the end state rather than the source. Built for designers who want to act on the rendered result without going through a developer.
LoupeKit
Free tier · nine surfaces · Chromium and Firefox
A reader rather than an editor. It answers what the page is built with, what its tokens are, what it ships, what it fails and how much of it reads as generated - and its own editing is deliberately shallow: inspect and adjust a property, undo-stacked, never persisted.
Feature by feature
6 of 10 rows differ · they are the shaded onesWhere LoupeKit stops, and why
2 of the rows above · each one is a decision- Design-tool hotkeys
- VisBug is a design tool that happens to run in a browser, and its key map is the one a designer already has in their hands. LoupeKit is a panel you read, so its shortcuts open surfaces rather than nudge elements.
- Open source
- The source is not published. What is checkable without it is stated instead and can be verified from the store listing: the permission list is four entries with no host permissions, and every request the extension makes is named on the privacy page.
The same jobs, side by side
Nudge an element and see how it looks
VISBUG The product. Keyboard-driven, fast, and made for exactly this.
LOUPEKIT Edit a property in place, or step the element itself in four directions - and a marquee band applies one change to everything it caught. Undo-stacked, never persisted, and driven by controls rather than by hotkeys.
Measure the distance between two things
VISBUG Point at one, hover the other. Excellent.
LOUPEKIT Comparable, plus the distances to each viewport edge.
Try a different typeface across the page
VISBUG Adjust type on what you select.
LOUPEKIT Swap the family everywhere and see whether the real one ever loaded.
Find out what the page is built with
VISBUG Not what it is for.
LOUPEKIT 1700 technologies with the evidence for each.
Find every element that overflows the viewport
VISBUG Not offered.
LOUPEKIT A ranked list with the cause named per row.
Get the page’s design system out as a file
VISBUG Not offered.
LOUPEKIT Colours, families, spacing, radii, type steps and shadows as a Tailwind theme, CSS sheet or W3C token file.
Pick VisBug if
If the job is to change what is on screen - moving things, aligning them, trying copy, adjusting type at a real device width. It is built around that loop, the hotkeys are the whole experience, it is free, and its source is public so you can see exactly what it does. There is no version of this comparison where paying for something else to do that is the better call.
Pick LoupeKit if
If the job is to find out what the page is, rather than to change it: what built it, what it ships, where it breaks, and how much of it reads as generated.
Run both
The natural arrangement, and free on both sides. Read the page with one, push it around with the other.
TWO BUILDS9 browsers
Chromelisting in reviewFirefoxlisting in reviewBravelisting in reviewOperalisting in reviewEdgelisting in review4 moreChromium browsers: Arc, Vivaldi, Chromium, Opera GXthe Chrome buildCHECKED 17 AUGUST 2026
Every figure about VisBug on this page was checked on that day against its published manifest and README in the project repository, and nothing here is quoted from a review. Where a fact is not published anywhere we can point at, the table says so rather than estimating it. Products change; if something above is out of date, write to [email protected] and it will be corrected.
VisBug and every other product name on this site are the trademarks of their own owners. LoupeKit is not affiliated with, endorsed by or sponsored by any of them.