Overview

This section highlights the core features, use cases, and supporting notes.

Everything is a Windows filename search engine for users who want instant file and folder lookup across busy local drives, with fast NTFS indexing, practical search syntax, and optional folder indexing for network shares or other non-NTFS locations. Its real strength is dependable low-overhead file discovery, not flashy document analysis, which is why it remains one of the most useful Windows file search tools for people who work with large folder trees every day.

Everything is best understood as a purpose-built Windows file search utility, not as a general desktop assistant and not as a content-heavy document search platform. The official voidtools support page describes it as a filename search engine for Windows, and that wording matters because it explains why the software feels so fast. Everything is optimized around file and folder names, path data, and a lightweight index that updates in real time. For anyone searching for an instant filename search tool for Windows, a fast file finder for large drives, or a cleaner replacement for slow Explorer search, that focus is exactly the reason the software earns a permanent place in daily use.


Annotated screenshot of the official Everything support page showing the tool as a fast Windows filename search engine with a small footprint
This overview screenshot is worth showing because it captures Everything’s core promise in one place: very fast Windows file search with low overhead. Click the image to open the full-size screenshot.

The installation choices are also more meaningful than they look at first glance. The official Installing Everything guide says the installer is recommended, explains the difference between installer and portable builds, and shows that NTFS indexing can be handled through the Everything service, by running as administrator, or be disabled entirely. That is practical information, not filler. It helps users choose a setup that matches how they actually work. If you want a Windows search app that behaves well as a normal daily utility, the recommended service-based path is easier to live with than guessing later why indexing behaves differently across machines.


Annotated screenshot of the official Everything installation guide showing installer choices and NTFS indexing method options
The installation screenshot matters because it shows that choosing installer versus portable and the NTFS indexing method affects how smooth the first setup feels. Click the image to open the full-size screenshot.

The first-run experience is where Everything usually wins people over. The official Using Everything page says an index of all local NTFS volumes is created the first time the app runs, that indexing takes only a few seconds, and that once the stage is complete all files are displayed and partial filename search begins instantly. The same page also documents useful starter habits such as searching dm:today for files modified today and sorting by Date Modified to watch changes in real time. This is one reason Everything works so well for developers, operators, researchers, and office users with large local file sets: the first useful result arrives quickly instead of demanding a long setup ritual.


Annotated screenshot of the official Using Everything guide showing first-run NTFS indexing and instant partial-name search
This usage screenshot earns its place because it shows the practical starting point: Everything builds its NTFS index first, then partial filename search becomes immediate. Click the image to open the full-size screenshot.

Where Everything becomes more than a fast launcher is its search syntax. The official Searching guide shows partial filename search, drive limits such as d:, quoted path search such as "c:program files", and core operators including space for AND, | for OR, and ! for NOT. The same page lists modifiers like file:, folder:, path:, regex:, and wholeword:, plus quick macros such as audio:, doc:, pic:, and video:. That is why Everything is stronger than a plain filename box. It gives power users a real Windows search syntax without turning the interface into a heavyweight database application. For people searching terms like Everything search syntax, Windows search by path, or instant file filter by type, this part of the product is a major reason to keep it installed.


Annotated screenshot of the official Everything searching guide showing path search, operators, modifiers, and file-type macros
The search-syntax screenshot is valuable because it shows where Everything moves beyond basic lookup into precise path, operator, and file-type filtering. Click the image to open the full-size screenshot.

The indexing model is also worth understanding before you overload the app with expectations it was never trying to meet. The official Indexes page says that by default Everything indexes all local fixed NTFS volumes, always indexes name and path information, and treats extra information such as file size, dates, and attributes as optional. It also notes that indexed information can be searched instantly, while extra information that is not indexed is gathered on demand and can be quite slow for many results. That tradeoff is the heart of Everything’s design. You get extreme speed by default, and then you opt into richer metadata only when it is worth the extra memory. The docs also show the database location under %LOCALAPPDATA%EverythingEverything.db, which is a useful detail for users thinking about backup, portable habits, or troubleshooting.


Annotated screenshot of the official Everything indexes guide showing default NTFS indexing and optional metadata indexing tradeoffs
This indexes screenshot is important because it explains Everything’s speed model: instant name and path search first, optional extra metadata second. Click the image to open the full-size screenshot.

Everything is not limited to ideal NTFS desktops either, but its expansion path comes with realistic tradeoffs. The official Folder Indexing page says folder indexing can include network shares, mapped network drives, FAT32 volumes, and any physical file-system folder. It also says folder indexing does not require administrative privileges or the Everything service, but it uses the same approach as Windows search and can be much slower than NTFS indexing. That is exactly the kind of nuance a useful software page should preserve. If your real problem is searching NAS folders, removable drives, or mixed storage locations, Everything can still help, but the performance story will not be identical to local NTFS volumes.


Annotated screenshot of the official Everything folder indexing guide showing support for network shares and non-NTFS folders with slower scanning
The folder-indexing screenshot deserves space because it shows how Everything can reach network shares and non-NTFS folders while making the speed tradeoff explicit. Click the image to open the full-size screenshot.

Our grounded view is that Everything is worth installing if your main pain point is finding files and folders quickly on Windows, especially across large local NTFS drives where Explorer search feels inconsistent or slow. It is weaker if you expect semantic document understanding or a polished cross-device knowledge system. In short, Everything is strongest as an instant Windows file finder with a mature search language and practical indexing options, and it becomes even more valuable when you treat it as a precision tool for daily file retrieval rather than a magical search engine for every kind of data.

Setup / Usage Guide

Installation steps, usage guidance, and common notes are maintained here.

The best way to set up Everything is to keep the first pass practical: choose the right build, let the initial index finish, learn a few search patterns that save time immediately, and only then decide whether you need deeper indexing or network-share coverage.

  1. Open the official voidtools site from the button on this page and start from the official download and support path. If you just want a normal long-term Windows setup, the official installation guide recommends the installer version, while the portable build makes more sense only if you specifically want a self-contained folder-based setup.
  2. Choose the correct architecture before you install. The official docs explain that x64 requires a 64-bit Windows system and supports larger databases, while x86 works on both x86 and x64 Windows but follows x86 context-menu limits. If you are unsure on a modern PC, x64 is usually the sensible choice.
  3. During installation, pay attention to how NTFS indexing will be handled. The official guide shows three paths: install the Everything service, run Everything as administrator, or disable NTFS indexing. For most users who want full NTFS indexing without running the app elevated every day, the recommended service-based path is the cleanest choice.
  4. Finish the install, launch Everything, and let the first index complete before judging the tool. The official usage guide says local NTFS volumes are indexed on first run and that the process usually takes only a few seconds. Waiting for that first pass is what turns the app from a blank window into an instant file finder.
  5. Test one simple real query first. Type part of a filename you know exists and confirm that the result list reacts immediately. This first success matters because Everything is most useful when you start trusting it for real work instead of treating it like another utility you might configure someday.
  6. Learn three high-value searches early: a drive-specific search like d:, a quoted path search like "c:program files", and a recent-change search like dm:today. These examples are grounded in the official docs and give you fast wins for common daily tasks.
  7. Use sorting deliberately. After a query such as dm:today, sort by Date Modified to inspect the newest changes first. The official usage page also notes that Everything tracks run count, which can help frequently used files rise to the top when you repeatedly open the same tools or project assets.
  8. Only enable extra indexed metadata after the basic search habit is working. The official indexes guide says name and path are always indexed, while file size, dates, and attributes are optional and require more memory. If you need instant filters or sorting on those fields every day, index them. If not, keep the lighter default and avoid unnecessary overhead.
  9. If you work with NAS paths, mapped drives, removable media, or FAT32 folders, add them through folder indexing instead of assuming they behave like NTFS volumes. The official folder-indexing guide makes two important points: this mode does not require administrative privileges or the Everything service, but it can be much slower than NTFS indexing.
  10. Review where Everything stores its data if backup or portability matters in your workflow. The official docs show that the database location can be changed from the Indexes tab, and the install guide also discusses where settings and data live. That is worth checking before you build habits around one machine.
  11. Do one final real-world test before deciding the tool is set up well: find a recent export, installer, config folder, or project file under time pressure. If Everything consistently gets you there faster than Explorer search, keep it in your daily workflow. If your needs are mostly content-heavy document search, lower expectations and use it mainly for the filename and path tasks it handles best.

A practical long-term setup usually looks like this: install the recommended build, let the NTFS index finish, learn partial-name and path search, add one or two favorite query patterns, and only then expand into metadata indexing or network-share folders. That sequence preserves Everything's main advantage, which is speed without operational clutter.

Related Software

Keep exploring similar software and related tools.