How to find a word on a page?

The fastest way to find a word on a page is to use the browser’s or app’s built-in “Find on page” option, rather than manually scrolling through a long text. This works well for terms and conditions, instructions and articles, when you need to get straight to a specific passage (e.g. “VAT 23%” or “return”). In practice, the biggest time saving comes from knowing the keyboard shortcuts and the method for moving between matches. It is also worth remembering what to do when a page is dynamic, contains embedded elements or runs in “infinite” scrolling mode. Below you’ll find specific steps for desktop computers and mobile devices, plus short workarounds for the most common limitations.

How to search for words on a page effectively in desktop browsers?

On a computer, the quickest way to search for a phrase on a page is to use Ctrl+F (Windows/Linux) or ⌘F (macOS), then type it into the “Find on page” field. Once the function is activated, a search bar appears in the top right-hand corner, where you can type e.g. “terms and conditions” or “VAT 23%”. You move between matches with Enter, and backwards with Shift+Enter. In most browsers you will see a counter in the form of “3/17”, so you can immediately see how many occurrences were found and which one you are currently on.

• Ctrl+F / ⌘F – launches “Find on page” and sets focus in the search field.
• Enter – go to the next match; Shift+Enter – to the previous one.
• F3 (often in Chrome/Edge/Firefox) – go to the next occurrence without selecting the field again.
• Ctrl+G / Ctrl+Shift+G (Firefox) – next/previous result for faster browsing.

When shortcuts are not an option, you can use the browser menu: in Chrome choose ⋮ → “Find…”, and in Edge … → “Find on page”. In Edge, the arrows in the search field can be used to move between results, and the browser can highlight all occurrences in the content and on the scroll bar. In Firefox, “quick find” also works, launched with /, which lets you start searching without taking your hands off the keyboard. If Ctrl+F is intercepted by the site or another programme, the “Find…” option in the menu is usually the most reliable alternative.

If a page is cluttered with elements, it can help to switch on reading mode (e.g. Firefox Reader View or Safari Reader) and search in the simplified view. This mode often removes menus, adverts and comments that “dilute” the results and make it harder to hit the right paragraph. When the content is generated by scripts or you are looking for a piece of HTML or a CSS class, open the developer tools (F12) and use search in the Elements/Sources panel (usually Ctrl+F). This lets you find e.g. the “data-price” attribute or the “.price–promo” selector, even if they are not visible in the page content.

1. 01Key shortcutCtrl+F or ⌘F
2. 02Search barEnter the phrase, results counter
3. 03Navigation and highlightingEnter, Shift+Enter, highlight
4. 04Access via menu“Find” option in the menu

The fastest way is keyboard shortcuts, which allow you to search content and navigate the results instantly.

Searching on mobile devices: Android and iOS

On a phone or tablet, you can find a word on a page using the “Find on page” option available in the browser menu. In Chrome on Android, choose ⋮ → “Find on page”, enter the phrase, then use the arrows to move between matches while keeping an eye on the results counter. In Firefox on Android, it works similarly and is especially useful when manually scrolling to a specific paragraph on a small screen becomes awkward. In Microsoft Edge on Android and iOS, this feature is in the … menu as “Find on page”.

In Safari on iOS/iPadOS, “Find on page” can be used in two ways: scroll to the top, tap “Share” and choose “Find on page”, or type the phrase in the address bar and in the results go to the “On this page” section → “Find: …”. If a link opens in an app’s built-in browser (WebView, e.g. in Facebook, Instagram or Gmail), search may be hidden or completely unavailable. The simple workaround that most often works is to use “Open in browser” (Chrome/Safari) and only then launch “Find on page”. This saves time when you need to quickly locate e.g. “return” in a shop’s terms and conditions.

On pages with infinite scrolling, search usually covers only the currently loaded part of the content. If it cannot find the word, scroll down, wait for more sections to load, and launch “Find on page” again. When typing a phrase on a phone, it is also worth watching out for autocorrect, as it can change the wording and distort the results (e.g. “faktura” → “faktury”). In such a situation, you can temporarily switch off autocorrect or type the phrase in a notes app and paste it into the search field to preserve the exact characters (e.g. “ą/ę/ł/ń”).

If a page is heavy and responds slowly, it can help to switch on Reader mode first and only then use search. In this view, the text is often converted into a simpler layout, which reduces the risk that part of the content will be unsearchable because of dynamic elements. Mobile browsers usually show up/down arrows and a counter such as “1/9”, which makes it easier to move through matches in long documents. If you need to enter a difficult name (e.g. a model or surname), you can also dictate the phrase in the search field using the keyboard microphone.

Advanced search techniques: matching, variants and multiple terms

You will get the best results when searching “on the page” if you match the query to how the given fragment actually appears in the content, taking into account letters, diacritics and formatting. Most browser find tools do not distinguish between upper- and lower-case letters, so “Faktura” and “faktura” are usually treated identically. However, when full precision is needed, for example with identifiers in code, it is more convenient to use developer tools or a text editor, where it is easier to enable case-sensitive matching. If you want an “exact” match, first copy the fragment from the content and paste it into the search field instead of typing it manually.

In practice, problems with matches often result from Polish characters and inflection, because “zalozenie” will not find “założenie”, and “reklamacja” may not hit “reklamacji”. If you do not have a Polish keyboard, copy the correct spelling from the page, if it can be selected, and use it in the search. In PDFs and in some layouts, text is split at the end of a line, e.g. “re-” + “klamacja”, so searching for the full phrase will not always work. In such cases, it helps to search for a shorter stem, e.g. “reklam”, and manually step through the results.

• If you suspect invisible formatting (e.g. a non-breaking space), start by searching for a single word (e.g. “Nr”), and only then check the context next to the result.
• When the content is embedded in an iframe, click inside the embedded document area and only then start the search, because otherwise you may only be searching the page “frame”.
• If you need two terms at once, remember that standard “Find on page” does not support AND/OR. First search for the rarer word (e.g. “odstąpienie”), and then check the second condition (e.g. “14 dni”) in the found paragraph.
• When working with numbers and codes, enter shorter, unique fragments (e.g. 6–8 digits), because the formatting (spaces, hyphens) may differ in the view from the HTML.

When you need to find a pattern rather than a specific word (e.g. dates in the format 2026-..-..), browser extensions that support regex or regex search in DevTools (in some panels) can help. On pages with tables, search can jump between cells according to DOM order, which makes orientation harder. If a table has its own filter (e.g. a “Search” field in DataTables), it often narrows down rows more effectively than standard browser search. This approach is particularly useful in price lists and long record sets.

1. 01Exact matchLetter and character matching
2. 02Case sensitivityBrowser vs editor
3. 03Polish charactersWord inflection as a keyword
4. 04Copy, don’t typeFor full precision

The key to success is to match the query precisely to the content, taking into account characters and formatting.

Troubleshooting search: what to do when it does not find anything?

When search does not find a word, it usually means the content is not “real” text, is hidden or has not loaded yet. If the word is visible on screen and yet there are no results, it may be a graphical element (e.g. a banner), so standard search will not cover it. In such a situation, it is worth using OCR, e.g. Google Lens in Chrome/Android, “Live Text” in iOS or the Tesseract tool. If the text is an image, only recognition (OCR) will make searching for a specific phrase meaningful.

If the content is hidden in an accordion (FAQ) or in tabs, some browsers may not search it until that section is expanded. You need to expand all modules (sometimes there is a “Show all” button) and then repeat the search. In SPA applications (React/Vue), delayed rendering of content can also be the issue, so a search started too early will not show any results. It is worth waiting until the data loads (e.g. the spinner disappears), or refreshing the page and trying again.

When Ctrl+F opens a different search window than expected, the page may have intercepted the shortcut and replaced it with its own “Find” function. In such a situation, it can help to find the “Find” option in the application’s own menu or use the “Find…” item from the browser menu as a workaround. If the search bar does not appear at all, the cause may be an extension (e.g. script blockers) or kiosk mode in a company browser. To quickly confirm the source of the problem, it is worth opening the page in incognito mode without add-ons or in a different browser.

If results exist, but it looks as if the browser is “missing” them, the highlight may be going under a sticky header. Usually it is enough to scroll slightly up or down, or move to the next or previous result, to see the correct fragment. It also happens that the searched spelling differs in the characters used (e.g. “smart” quotation marks “ ” or a long dash — instead of -), which means the character you type does not match the content. In such a case, it is best to copy the exact character from the page and paste it into search, or look for a fragment without special characters.

When trying to find data entered into a form, remember that browser search does not always include values in editable fields (inputs). If it is essential to find a specific entered value, searching within the field itself (where possible) or copying the content into Notepad and searching it outside the page may be more effective. A lack of results may also be due to inflection of the word (“konto” vs “konta”, “dzień” vs “dni”). In practice, it is often best to search for the stem (e.g. “reklamac”) and only then match the correct form in context.

Searching in documents: PDF, Word, Google Docs and e-books

In documents, the easiest way to find a word is to use the built-in function in the relevant application (PDF/Word/Google Docs), because it works across the whole file and copes better with long content. When a PDF opens in the browser, Ctrl+F/⌘F usually works much like on a web page, but the number of matches may be smaller if the document contains scans rather than “real” text. In Adobe Acrobat Reader, Ctrl+F searches the current page, whereas Ctrl+Shift+F can search the entire document and show a list of results, which makes it easier to work with, for example, a long contract. If the PDF is a scan (an image), search will not work until you run OCR and a text layer is created.

When you need to “unlock” search in a scanned PDF, OCR in a tool that recognises text from an image will help. In practice, you can use Adobe Acrobat Pro (“Recognise Text”), and free of charge also Google Drive: open the PDF and choose “Open with Google Docs” to obtain a searchable version. Alternatively, you can use Tesseract OCR if you prefer a browser-independent solution. After text recognition, searching for phrases again (e.g. “kara umowna”) works just like in a normal document.

In Microsoft Word, you can find a phrase fastest with the Ctrl+F shortcut, which opens the navigation pane with a list of results and highlights in the text. If you want to work with variants (e.g. “reklamacja/reklamacje”), use “Find and Replace” (Ctrl+H) and consider searching with wildcards. In Google Docs, Ctrl+F works within the document, and Ctrl+H opens “Find and replace” with additional options, which is useful, for example, when correcting date formats (“2025-01-…”). For batch changes in content, “Find and replace” is faster than moving through matches manually.

On e-book readers (Kindle, Kobo, PocketBook), the “Search” function usually covers the whole book, but with large EPUB/MOBI files it may be sluggish. If it cannot find a term, the cause is often that the text has not been properly indexed or there are conversion errors from PDF that can split words. Presentations and spreadsheets have additional limitations: in PowerPoint, Ctrl+F jumps between slides, but it may skip text in speaker notes, and in Excel it is worth setting “Look in: values/formulas” and the scope (worksheet vs workbook). Such settings help when the searched phrase appears in formulas (e.g. “SUMA”), rather than in visible numbers.

If a page has been saved as a .html file on disk, it can be searched almost the same way as on the internet. Just open the file in a browser and use Ctrl+F/⌘F. This is handy when working with archives (e.g. a saved terms and conditions document), even when the original version of the page has later been changed or removed. In note-taking apps (OneNote, Evernote, Apple Notes), search covers entire notebooks and tags, which is often faster than browsing individual pages. What is more, Evernote and OneNote can perform OCR on text visible in an image within a note, so you can also search for words in photos.

1. 01Built-in functionWhole file, long content.
2. 02Browser (Ctrl+F)Works like on a page.
3. 03Advanced (Acrobat)Entire document, list of results.
4. 04Scans and OCRRequires a text layer.

Key methods for effective searching across different types of documents.

Accessibility and convenience: keyboard, screen readers, voice

It is easiest to search for a word without using the mouse when, after launching “Find”, you start typing straight away in the field, because focus is usually placed there automatically. If focus “escapes”, it is worth using Tab/Shift+Tab to return to the field and then moving through the results with Enter. If highlights are hard to see, turning on high contrast in the system or changing the browser theme helps, making it easier to spot matches in the text. In some browsers (e.g. Firefox), the function that highlights all matches gives better orientation, because you can see a kind of “map” of the results on the page.

Screen readers (NVDA, JAWS, VoiceOver) usually work best with the browser’s built-in search, so it makes sense to use Ctrl+F/⌘F rather than relying solely on the reader’s own “find” commands. Once a match has been found, you can ask the reader to read the current line or paragraph so you can quickly check the context without looking at the screen. At high zoom levels (e.g. 200–300%), the page layout can reflow, which makes it harder to orient yourself after jumping to a result. When it is easy to lose context, it can help to reduce the zoom by one step (Ctrl+-) or switch to reading mode, where text reflow is often more stable.

On a phone, entering a phrase can be sped up by dictating it into the “Find on page” field (keyboard microphone). This is particularly useful with long names (e.g. models such as “WH-1000XM5”) or surnames, where a typo immediately ruins search results. When a heavy page on iPhone runs sluggishly, enabling Reader in Safari often improves the smoothness of moving between matches and “cleans” the results of repetitive elements (menus, footers). If moving between results is cumbersome, reading mode can genuinely simplify navigation and reduce “noise” in the results.

If the page has a table of contents (TOC) with anchors, it is sometimes quicker to click the section heading than to wade through hundreds of search hits. For screen reader users, navigating by headings (H) is also convenient, while using search as a way to pinpoint a specific word. It is also worth remembering the impact of translation on the page. When automatic translation is enabled (e.g. Google Translate in Chrome), the text on screen may differ from the source, which affects search results. If you cannot find a phrase in Polish, it is worth searching in the original language (e.g. “privacy policy”) or turning off translation and repeating the search.

When comparing two fragments of the same page, it can be practical to open it in two windows side by side and check the same phrase in each of them. This layout makes it easier to compare information (e.g. a definition and a table) without constantly going back to one place. In practice, it also reduces the risk of losing context after moving to the next result. This small improvement is especially useful when analysing specifications, where “requirements” and “exceptions” are quickly checked on one screen.

Tools and automation: when you need more than Ctrl+F

If you need to find a word not on one page, but across an entire website or in content that disappears over time, instead of Ctrl+F you can use Google Search with the site: operator. In practice, you enter a query such as: site:twojadomena.pl “kara umowna”, to quickly determine on which subpage a given phrase appears. If the content may have been changed or removed, it is also worth checking Google cache (“Copy”) or archive.org, because an earlier version of the page may be available there. This approach works particularly well when you do not remember the exact subpage URL.

When the goal is not only to “jump” between results, but also to view them as a list or count occurrences, browser extensions such as “Find+ | Regex Find” come in handy. Such add-ons can display a list of matches, which makes it easier to move quickly to the right context (e.g. checking how many times “opłata manipulacyjna” appears). When working with long pages, a convenient alternative is also to copy the content (Ctrl+A → Ctrl+C) into Notepad++ or VS Code, where search works more efficiently and offers additional options (match case, regex, select all occurrences). This solution avoids situations where the page interface makes it difficult to hit a match precisely.

When you need to find something in code, scripts or page assets, rather than limiting yourself to visible text, it is worth using developer tools. In Chrome/Edge DevTools, you can use “Search in all files” (often Ctrl+Shift+F) in the Sources tab to search loaded files for phrases such as endpoint /api/v2/orders or the presence of a tracking pixel. On static pages, you can also download the HTML with curl and filter it with grep/ripgrep (e.g. curl -s URL | rg “polityka prywatności”), which lets you quickly check whether a given word appears in the source. This solution is especially useful when the page UI runs sluggishly or can be unstable.

If such checks need to be carried out regularly or you need to compare content versions, automation and working with files is often the most practical approach. Playwright or Selenium make it possible to retrieve content and verify, with assertions, the presence of messages (e.g. “incident” or “degraded performance”) at fixed intervals, and when asking “has this word disappeared after the update?” you can save two versions of the page and use a diff tool (WinMerge, Meld, VS Code). For local PDFs, pdftotext (the poppler package) converts the document into text, which can then be searched with grep (e.g. pdftotext umowa.pdf – | rg “odstąp”). When working with sensitive content (PESEL, account numbers), it is better not to paste data into external “online OCR” services or unknown extensions. It is safer to rely on local tools and offline mode.