gpsoft.com.au

Indexing improves file management by pre-building a map of which words appear in which files, so a desktop search tool can answer content queries in milliseconds instead of scanning every file on every search. In DocFetcher, an open-source desktop search application for Windows, Linux, and macOS, you create an index once per folder you want to search. After that, searches run against the index rather than the raw files, and updating the index after files change typically takes only a couple of seconds.

Why scanning files directly doesn't scale

Without an index, finding a document by its contents means opening files one by one and checking for your search terms. That works for a handful of files but breaks down across a whole drive: the cost grows with the total number and size of files, and every new search repeats the same work.

An index changes the economics. DocFetcher builds a lookup structure that records which files contain a particular set of words, so a query resolves in the order of milliseconds regardless of how many files sit behind it. The trade-off is upfront work: building the index takes time, but only once per folder.

How indexing works in DocFetcher

DocFetcher requires you to create indexes for the folders you want to search — it does not search arbitrary locations without one. The workflow is:

1. Choose a folder you want to make searchable.
2. Create an index for it through DocFetcher's index-creation dialog.
3. Run the indexing process, which reads the files and records their contents.
4. Search normally afterward; queries hit the index, not the files.

The indexing step can take a while depending on how many files you include and how large they are. A useful planning figure from the project's own documentation is roughly 200 files per minute. So a folder of 2,000 documents is on the order of ten minutes of indexing — a one-time cost, not a per-search cost.

Creation is slow, updates are fast

The important asymmetry: creating an index takes time, but updating it after the folder's contents change is much faster — usually just a couple of seconds. This is what makes indexing practical for active folders. You pay the full price once, then pay a small price each time you add, edit, or remove files.

What you can do once files are indexed

Indexing is the enabler; the search interface is where it pays off. In DocFetcher's main window, queries go into a text field, results appear in a result pane, and a preview pane shows a text-only view of the selected file with all matches highlighted in yellow.

You can narrow results along three independent dimensions:

Combining these turns a broad content query into a short, relevant list — for example, a term plus a file-type filter plus a location filter to isolate one project folder.

Portable indexes for file management on the move

DocFetcher offers portable versions for Windows, Linux, and macOS. These let you build a portable document repository: a fully indexed, fully searchable collection of your documents that you can move freely. Practical uses include carrying it on a USB drive, packaging it for archival, placing it inside an encrypted volume, or synchronizing it between computers through a cloud drive.

This is the clearest illustration of why indexing matters for file management: the expensive part (building the index) travels with the documents, so search stays fast wherever the repository goes.

When indexing is worth it — and when it isn't

Indexing pays off when:

• You repeatedly search the contents of many files, not just filenames.
• The folder is large enough that manual scanning is impractical.
• The folder changes often enough that fast updates matter (they do — updates are seconds, not minutes).

It may not be worth it when:

• You only need to search a few files occasionally.
• The folder changes so rarely that a one-time index still sits unused.
• You need multi-user access or a web interface — the project points to DocFetcher Server, its commercial variant, for multi-user support, and to DocFetcher Pro for additional features beyond the open-source edition.

For a single user searching local documents on one machine, the open-source DocFetcher covers the core case: index once, search in milliseconds, update in seconds.

ShadowExplorer is a graphical front end for the Windows Volume Shadow Copy Service (VSS). It lets you browse the point-in-time Shadow Copies that Windows creates automatically and retrieve older versions of files you have deleted or modified. It works with Windows 11, 10, 8, 7, and Vista, and is primarily intended for users of Home editions, who do not have access to Shadow Copies by default. It is not a backup tool: Shadow Copies live on the same disk as the original data, so a disk failure destroys both.

How Windows Shadow Copies work

From time to time, Windows creates point-in-time copies of your files through the Volume Shadow Copy Service. These snapshots let you recover a file as it existed at an earlier moment — useful when you have accidentally deleted or overwritten something.

The service is included in all Windows editions and enabled by default. The catch is access: Microsoft only grants built-in access to these copies in the Ultimate, Business, and Enterprise editions. On Home editions the copies exist but there is no standard way to reach them.

ShadowExplorer fills that gap. It is an additional tool that accesses the shadow storage and makes the point-in-time copies visible to the user, without changing how VSS itself works.

What you can do with ShadowExplorer

According to the project's own description, its features are:

• Show available point-in-time copies
• Browse Shadow Copies
• Retrieve versions of files and folders

In practice, the workflow is: pick a point in time, navigate the shadow copy the same way you would browse a normal drive, and copy out the version of the file or folder you want. This is the same underlying data that the "Previous Versions" feature exposes on editions where Microsoft enables it.

The limitation you must not ignore

ShadowExplorer's own documentation is explicit: Shadow Copies and ShadowExplorer are in no way a replacement for regular backups. A Shadow Copy is stored on the same disk as the original data. If that disk fails, all data is lost, including the Shadow Copies.

Treat ShadowExplorer as a good addition to regular backups, not a substitute for them. It helps with the common case — a file deleted or edited by mistake while the disk is healthy. It does nothing for you when the disk itself dies.

When to use it

For more background on the service itself, the site points to Microsoft's documentation on Shadow Copy.