SharePoint search works through a search bar that appears at the top of every SharePoint page, but where you start your search determines what results you see. Typing a query on the SharePoint start page searches across all content you have access to, while searching from a specific team site only returns results from that site. Understanding how scope, syntax, and filters work will help you find documents, pages, and files far more quickly.
Where You Search Changes What You Find
SharePoint uses different default scopes depending on which page you’re on when you type your query. On a regular team or communication site, the search bar scopes results to that single site. On a hub site (a site that connects several related sites together), search covers all sites within the hub. On a home site or the SharePoint start page, search covers all content across your organization that you have permission to view.
This matters because the most common reason people can’t find a file is that they’re searching from the wrong starting point. If you know a document lives on a specific project site, navigate there first and search from that page. If you’re not sure where something lives, go to the SharePoint start page (sharepoint.com in your browser) and search from there to cast the widest net.
Searching Inside a Specific Library or Folder
When you need to find something inside a particular document library, navigate to that library first. The search bar on that page will search within the library by default. If you start a search from the site’s home page instead, you can narrow results after the fact by changing the scope to “This List” or “This Library,” which restricts your query to just that collection of files.
SharePoint does not offer a built-in way to search a single subfolder directly from the search bar. The practical workaround is to search from the library level, then sort or filter results by the folder path in the file’s location column. For deeply nested folder structures, using metadata columns or tags on your files is far more reliable than relying on folder hierarchy.
Using Search Operators for Precise Results
SharePoint supports a query syntax called Keyword Query Language (KQL) that lets you build precise searches directly in the search bar. The syntax is case-insensitive for your search terms, but the operators themselves (AND, OR, NOT) must be typed in uppercase.
The most useful operators for everyday searching are property restrictions, which let you search specific fields of a document rather than all of its content. The format is the property name, a colon, and the value, with no spaces between them:
- author:”Jane Smith” returns files authored by Jane Smith
- filetype:docx returns only Word documents
- filetype:pdf returns only PDFs
- filename:budget.xlsx returns a file with that exact name
You can combine these with Boolean operators. Searching author:"Jane Smith" AND filetype:docx returns only Word documents written by Jane. Searching project plan OR project proposal returns results containing either phrase. Adding NOT filetype:pptx excludes PowerPoint files from your results.
Wildcards work at the end of a word but not the beginning. Searching budget* will match “budget,” “budgeting,” and “budgets.” But *budget will not work as a prefix search. If you need to find an exact phrase, wrap it in quotation marks: "quarterly budget review".
Filtering Results After You Search
After running a search, SharePoint displays filter options along the top or side of the results page. These typically include file type, author, date modified, and the site or location where the file lives. Clicking any filter narrows your results instantly without changing your original query.
Your organization’s SharePoint admin may have set up additional filters called refiners, which are based on custom metadata properties. For example, if your company tags documents with a “Department” or “Project Name” column, those might appear as filter options in search results. These refiners only work on managed properties that have been configured as refinable in the search schema, so the available filters vary by organization.
SharePoint also offers vertical tabs at the top of search results, typically labeled “All,” “Files,” “Sites,” “News,” and “People.” Clicking “Files” immediately limits results to documents, while “People” searches the company directory. These verticals are the fastest way to narrow a broad search.
What SharePoint Can and Cannot Search
SharePoint indexes the full text content of most common file types, including Word documents, Excel spreadsheets, PowerPoint presentations, PDFs, and plain text files. When you search for a word or phrase, SharePoint looks inside these files, not just at their titles or metadata.
For image files and scanned PDFs, SharePoint uses optical character recognition (OCR) to extract and index text. This works on common image formats like PNG, JPEG, BMP, TIFF, and GIF, as well as scanned and hybrid PDFs (files that contain both selectable text and images of text). Images embedded inside Word, PowerPoint, and Excel files are also scanned automatically. The extracted text becomes searchable just like any typed content.
There are a few limitations. Image files must be under 50 MB and between 50 x 50 pixels and 16,000 x 16,000 pixels. Only images uploaded after your organization’s admin enabled OCR are scanned, so older files may not have their image text indexed. And for PDFs and TIFFs, the OCR text is indexed for search but won’t appear in a metadata column, so you can find the file but won’t see the extracted text previewed in search results.
Tips That Save Time
Start broad, then narrow. Run your search from the SharePoint start page if you’re unsure where a file lives, then use the “Site” filter in results to see which site contains it. Once you know the location, you can search directly from that site in the future.
Use file type restrictions when you know the format. If you remember the document was a PowerPoint, adding filetype:pptx to your query eliminates noise from emails, Word docs, and PDFs that happen to share the same keywords.
Combine author and date when you remember who created something. Searching author:"Marcus Lee" and then filtering by date range in the results page is often faster than trying to remember the exact file name. If your organization uses metadata columns like project codes or client names, those properties can also be searched with the same property:value syntax, as long as your admin has made them available in the search schema.