Ctrl+F vs ctrlQuery: When Browser Search Stops Being Enough

Published May 27, 2026

The 80-match problem

You're reading the Wikipedia article on World War I, trying to find the section that explains what actually started the war. The page is 60 screens long. You hit Ctrl+F, type cause, and get 70 matches. Now you have to arrow through every single one. Half of them are noise: "because" in random sentences, "caused by influenza" from the section on the 1918 pandemic, "causal chain" in a footnote, and you're looking for the one paragraph that walks through the chain of events from the assassination in Sarajevo to the declarations of war.

You know the answer is on this page. You just can't find it in the haystack of literal matches.

This is the moment Ctrl+F stops being a tool and starts being a tax. The browser's built-in find is doing exactly what it was designed to do in 1995. It's matching strings. It has no idea what you're actually looking for, because string matching has no concept of "actually looking for" anything.

That gap between what you typed and what you meant is what I built ctrlQuery to close.

What Ctrl+F is, and what it isn't

Let me give Ctrl+F its due. It's one of the most-used keyboard shortcuts in computing for good reason.

It's instant. It's universal: every browser, every OS, no install, no account. It's free forever. It works offline. It's pre-loaded in the muscle memory of approximately everyone who has ever used a computer. There is no friction.

For the thing it does, it's close to perfect. If you know the exact string you're looking for, like a function name, an error code, or a person's last name, Ctrl+F is the right tool and ctrlQuery is overkill.

The trouble is that "the exact string I'm looking for" is the minority case for most real-world reading. Here's what Ctrl+F can't do:

• It only matches literal text. Search for "chill the dough" on a recipe that says "rest the dough in the fridge for two hours" and you get zero matches. The recipe contains your answer. Ctrl+F can't see it.
• It doesn't understand synonyms or paraphrases. "Cancel my subscription" and "terminate your account" describe the same thing. Ctrl+F treats them as unrelated.
• PDFs are a coin flip. Native PDF viewers often fail to index correctly, scanned PDFs have no extractable text at all, and even text-based PDFs frequently miss matches due to character-encoding weirdness.
• It doesn't see hidden content. Collapsed accordions, tabs you haven't clicked, content inside iframes, anything rendered into a shadow DOM by a modern web component. Ctrl+F walks right past all of it.
• It can only search for one thing at a time. No OR queries, no "find me anything that looks like a date," no filters.

None of this is Ctrl+F's fault. It was built for a different web. The web kept going.

What ctrlQuery does differently

ctrlQuery is a Chrome extension that adds a smarter find bar on top of the one you already have. Two modes.

Keyword Search is free. It's Ctrl+F if Ctrl+F could actually see the whole page, across iframes, into shadow DOM, through hidden tabs and collapsed accordions. It supports OR queries (error OR exception OR failure) and slash commands like /dates and /number to pull out every date or number on the page at once.

Smart Search is the AI part. You type a question or a concept, and it finds the passage that means what you asked, even when the words don't match.

A concrete example. Open the Wikipedia article for Ethan Hawke and Smart-Search the single word born. The word "born" does not appear in the heading "Early life and education," but that's the section that answers the implicit question. Smart Search ranks that section at the top. Ctrl+F sends you to the infobox, the first sentence, and a half-dozen unrelated places.

That's because Smart Search isn't doing string matching. The page gets chunked, each chunk becomes a 384-dimensional embedding using bge-small-en-v1.5, your query becomes an embedding, and a hybrid Orama index ranks chunks by both vector similarity and BM25 keyword score. Adaptive thresholding cuts off weak matches. Lexical rescue makes sure that if you searched for a specific word and it's on the page, you still get that hit.

The thing I want to be clear about: all of this runs on your machine. The embedding model is downloaded once via transformers.js, cached locally, and runs in the browser. Your page content is not sent to OpenAI. It is not sent to me. There is no telemetry, no account, no server-side anything. After the first install, Smart Search works offline on a plane.

A few other tools in this space do semantic search by shipping your page content to a cloud LLM. They're often very good, and the teams behind them are doing real engineering. They're also, by design, in a category I don't want ctrlQuery to be in. If you're searching internal docs, legal PDFs, medical research, or anything sensitive, "your page gets posted to a third-party API" is the wrong answer. (For a fuller competitive picture, see Best AI Ctrl+F Alternatives in 2026.)

ctrlQuery also has a custom PDF viewer built on PDF.js, so semantic search actually works on the documents where Ctrl+F most often falls apart. (See How to search a PDF semantically in Chrome for the walkthrough.)

Ctrl+F vs ctrlQuery: side by side

Ctrl+F wins on three rows that matter: it's instant, it's universally installed, and it's free. Those are real advantages. I don't pretend they aren't.

ctrlQuery wins everywhere the page is long, the wording is ambiguous, or the content is buried in something Ctrl+F can't see.

When to use which

Ctrl+F is the right tool when you know the exact string and you trust the page to render it normally. Looking up a function name in API docs. Finding a person's last name in a roster. Jumping to a specific error code in a stack trace. Locating a known headword on a page you wrote yourself. For these, ctrlQuery is overkill and I'd tell you to just use Ctrl+F.

ctrlQuery becomes the right tool the moment any of the following is true:

• The page is long enough that scrolling through Ctrl+F matches is a chore.
• You're not sure what word the author used. You know the concept, not the phrasing.
• The content is a PDF, especially a long or scanned one.
• The page has tabs, accordions, embedded iframes, or modern web-component UI where part of the content isn't visible until you click something.
• You want to extract a category of thing, like every date, every dollar amount, every email address, without reading the whole page.
• You're searching anything sensitive and don't want it posted to a third-party API.

A useful rule of thumb: if you'd describe what you're looking for to a colleague in a full sentence, that's a Smart Search query. If you'd just say one word and they'd know what you meant, that's a Ctrl+F query.

The two coexist. The Cmd/Ctrl+F shortcut still works exactly like it always did. ctrlQuery sits next to it, not on top of it.

Trying ctrlQuery in 30 seconds

1. Install ctrlQuery from the Chrome Web Store.
2. Open any page where you'd normally hit Ctrl+F. A long article, a PDF, a docs page.
3. Use the keyboard shortcut to open ctrlQuery, or click the toolbar icon.
4. Start in keyword mode. Try an OR query: error OR warning OR exception. Try a slash command: /dates.
5. Switch to Smart Search. Type a question instead of a keyword, something like "how does cancellation work" on the MDN AbortController page, or "what was his first film" on a Wikipedia actor page.

The first Smart Search on your machine triggers a one-time model download of around 30MB. After that, it's cached. Smart Search works on every page going forward without re-downloading anything, including offline.

If you don't like it, uninstall takes one click, and there's no account to delete because there was never an account to begin with.

Install ctrlQuery

FAQ

Does ctrlQuery replace Ctrl+F?
No, and it isn't trying to. Ctrl+F is great at what it does. ctrlQuery is a second tool for the cases where literal string matching isn't enough. They live side by side.

Does my page content leave my computer?
No. Embeddings are computed on-device using transformers.js running the bge-small-en-v1.5 model. The vector index lives in memory in your browser. Nothing is uploaded, no telemetry is collected, and there's no account system that could associate queries with you. With your network off, Smart Search still works after the first install.

Does it work on Mac?
Yes. ctrlQuery is a Chrome extension, so it runs on Chrome across macOS, Windows, Linux, and ChromeOS. It should also work on Chromium-based browsers like Edge, Brave, and Arc, though primary testing is on Chrome.

What if I just want a faster Ctrl+F and don't care about AI?
Use the free keyword mode. It already gives you cross-iframe search, shadow DOM support, OR queries, slash commands, and a working PDF viewer. No payment required, no Smart Search needed.

Is it free?
Keyword Search is free forever. Smart Search is a one-time $3.99 unlock. No subscription, no recurring charge, no upsell. The AI mode is paywalled because the model and viewer infrastructure still cost something to develop and maintain. Buy it once, own it.

Does it work on every site?
It works on essentially any standard webpage and on PDFs opened through Chrome. Some heavily sandboxed pages, like Chrome's own chrome:// internal pages, the Web Store itself, and a handful of banking sites with strict content security policies, block all extensions, including this one. That's a browser-level restriction, not a ctrlQuery limitation.

Try it

If you've ever scrolled through 80 Ctrl+F matches looking for the one paragraph that mattered, ctrlQuery is built for that exact moment. Install it from the Chrome Web Store, try the free keyword mode on whatever long page is open in another tab right now, and decide for yourself whether the smart Ctrl+F upgrade is worth the unlock.

Install ctrlQuery

Related

• Best AI Ctrl+F Alternatives in 2026: A Real Comparison
• How to Search a PDF Semantically in Chrome (Without Uploading It Anywhere)