Browser extensions, built in-house

Extensions worth the permissions they ask for.

We design and build a small number of browser extensions, and we document each one properly: what it does, the permissions it asks for and where your data goes. No accounts, no tracking, nothing uploaded behind your back.

What we build

Our extensions

Small tools that do one job properly, with no account, no upload step and a page that says exactly what each one touches.

See all

Go Full Screenshot

Built and maintained by us

Official

One click captures the entire page, then an editor with blur, arrows, mockups and PDF export.

Productivity Free ChromeEdge
  • Capture, editing and export all happen inside your browser
  • No account, no sign-in and no upload step
  • Images stay on your device until you copy or save them yourself

How we build

What every extension of ours does

An extension runs inside the browser you use for banking, work and email. That access deserves a higher bar than a five-star average, so these four rules apply to everything we ship.

  • The fewest permissions that work

    Every permission an extension of ours requests is one we could not do the job without, and each one is written out in plain language on its page before you install it.

  • Your data stays on your machine

    Our extensions do their work inside the browser. There is no server of ours in the middle, nothing is uploaded in the background, and nothing is sold to anyone.

  • No account, no sign-up wall

    You install it and it works. We do not ask for an email to unlock a feature, and we do not build a profile of the pages you visit.

  • No ads, no affiliate links

    Our extensions never inject advertising, coupons or rewritten links into the pages you browse. If an extension of ours ever costs money, the price is on its page.

Method

How an extension gets built

More about how we work
  1. 01

    One job, done properly

    Each extension solves a single problem end to end. We would rather ship one tool that finishes the task than a suite that half-does five.

  2. 02

    Built to the permission budget

    We design the feature around the narrowest permission that can deliver it, not the other way round. If a feature needs your whole browsing history, it does not ship.

  3. 03

    Documented before release

    Every extension gets a page like the ones here: what it does, what it touches, what it cannot do, and the limits worth knowing before you rely on it.

  4. 04

    Maintained after release

    Browsers change their extension platform constantly. We keep shipping updates and keep these pages in step with the version you actually have.

FAQ

Questions people ask

Something missing? Ask us directly — we answer in English and Spanish.

Who makes these extensions?

We do. Everything on this site is designed, built and maintained in-house by Extension.lat — this is not a directory of other people software, and we do not publish or host anyone else extensions.

Are they free?

Yes. Our extensions are free to install and use, with no trial period and no feature held back behind a sign-up. Where an extension ever has a paid tier, the price and what it unlocks are stated on its own page.

Do you track what I browse?

No. Our extensions work inside your browser, there is no account to create, and we run no analytics on the pages you visit. Each extension page lists exactly what it can reach and what it does with it.

Why does an extension need permission for all sites?

Some jobs cannot be done otherwise: capturing a page means reading that page. What matters is what happens next, which is why every extension page spells out the permissions requested and where the data goes — nothing leaves your device unless the feature you pressed requires it.

Which browsers do you support?

Chrome and Edge today, with the store links on each extension page. Firefox and Safari builds are added when we can support them properly rather than shipping a half-working port.

I found a bug, or I need a feature. What do I do?

Write to us. Bug reports and feature requests from people who actually use the extensions decide what we build next, and every message is read by the person who wrote the code.

Built by the people who answer the email.

There is no support queue and no ticket robot here. Bug reports and feature requests go straight to the person who wrote the code, and they are what decides which extension we build next.