FilePulse
Advanced File Search Engine
FilePulse is an ultra-high-performance search engine that searches both file names and contents with lightning-fast millisecond performance. The core search engine runs locally; it is fully portable and requires no installation. It supports rapid startup, quick preview, remote disk access, and comprehensively supports Windows, macOS, and Linux across both x86_64 and ARM64 architectures, allowing for the creation of cross-platform, cross-architecture distributed search clusters.
Contact Us
Key Features
File Name Search
Search using wildcard patterns, regular expressions, complete pinyin, and pinyin initial matching algorithms. Sort and filter by file size, folder size, modification time, file name, file path, and extension. Support prefix matching, suffix matching, full word matching, diacritic character matching, symbol-ignoring matching, whitespace-ignoring matching, case-insensitive matching, and more.
Content Search
Search for specific text content within files, supporting full-text regular matching, full-text wildcard matching, word-segmented regular matching, word-segmented normal matching, word-segmented prefix matching, and word-segmented fuzzy matching. Support custom filtering of content search using file name search results. Support no sorting, sorting by file name search results, and sorting by relevance score. Support generating highlighted hit areas and quick preview.
Cluster Mode Support
Search across entire cluster results in a cluster of up to 256 servers, with all server nodes being equal.
Complete Remote Control
All nodes can provide services via HTTP, and support multi-node mutual proxy mode, allowing users to access any node data from any location.
Lightning Fast
Advanced indexing technology ensures instant search results even across millions of files.
Multi-Format Support
Supports searching through documents, code files, PDFs, and many other file formats.
Platform Support
FilePulse runs natively on all major platforms with full feature support
Windows
x86_64Linux
x86_64macOS
x86_64 (Intel)Windows
aarch64 (ARM64)Linux
aarch64 (ARM64)macOS
aarch64 (Apple Silicon)Cross-Platform Cluster Search
- Build clusters with up to 256 nodes across different systems
- Search results globally sorted across the entire cluster
- All nodes are equal, access cluster-wide data from any node
Performance/Feature Comparison (Windows x86_64)
Test Environment: AMD 7900X, PCIe 4.0 SSD, Windows 11 24H2. User versions may be packed, leading to performance degradation. Media performance testing can apply for unpacked versions. In the future, when the verification mechanism is perfected, unpacked versions will be provided comprehensively.
File Name Search Comparison with Everything
Timing method: browser request query interface, server waiting response time, all speed tests are non-cached hits
| Test Item | FilePulse 2.0.1 Pro (with built-in folder size calculation and extension indexing) | Everything 1.4.1.1026 + folder size calculation + extension indexing | Everything1.5.0.1391a + folder size calculation + extension indexing |
|---|---|---|---|
| 2 million files full disk scan speed + build storage structure speed | 2.58 seconds | 5.73 seconds | 4.26 seconds |
| 2 million files query one case-insensitive letter and sort by modification time descending | 10.39 ms | 10.38 ms | 10.79 ms |
| 2 million files query two case-insensitive letters and sort by modification time descending | 9.28 ms | 13.44 ms | 9.21 ms |
| 2 million files query three case-insensitive letters and sort by modification time descending | 8.81 ms | 13.70 ms | 9.05 ms |
| 2 million files query pinyin one case-insensitive letter and sort by modification time descending | 16.65 ms | Not Natively Supported | Not Natively Supported |
| 2 million files query pinyin two case-insensitive letters and sort by modification time descending | 16.88 ms | Not Natively Supported | Not Natively Supported |
| 2 million files query pinyin three case-insensitive letters and sort by modification time descending | 16.17 ms | Not Natively Supported | Not Natively Supported |
| 2 million files query pinyin initial one case-insensitive letter and sort by modification time descending | 17.25 ms | Not Natively Supported | Not Natively Supported |
| 2 million files query pinyin initial two case-insensitive letters and sort by modification time descending | 17.08 ms | Not Natively Supported | Not Natively Supported |
| 2 million files query pinyin initial three case-insensitive letters and sort by modification time descending | 15.29 ms | Not Natively Supported | Not Natively Supported |
| HTTP1 protocol support | Supports HTTP1.1 | Only supports old HTTP1.0 | Only supports old HTTP1.0 |
| HTTP2 protocol support | Supports HTTP2 | Not Supported | Not Supported |
| HTTP3 protocol support | Supports HTTP3 | Not Supported | Not Supported |
| Complex logical expressions support | Supported | Supported | Supported |
| Regular expressions support | Supported | Supported | Supported |
| Dual filtering by file name and file path simultaneously | Supported | Not Supported | Not Supported |
| File size/folder size filtering/sorting | Supported | Supported | Supported |
| Modification time filtering/sorting | Supported | Supported | Supported |
| File name filtering/sorting | Supported | Supported | Supported |
| File path filtering/sorting | Supported | Supported | Supported |
| Extension filtering/sorting | Supported | Supported | Supported |
| Custom format filtering | Supported | Supported | Supported |
| Case-insensitive matching | Supported | Supported | Supported |
| Prefix matching | Supported | Supported | Supported |
| Suffix matching | Supported | Supported | Supported |
| Whole word matching | Supported | Supported | Supported |
| Diacritic character matching | Supported | Supported | Supported |
| Symbol-ignoring matching | Supported | Not Supported | Supported |
| Whitespace-ignoring matching | Supported | Not Supported | Supported |
| Network cluster file name search | Supported, supports up to 256 servers in a cluster, 256 machines can mount data from other nodes, each node is equal, optional tracking of target disk changes | Not Supported | Limited, must map remote drives to local drive letters, not only occupying precious local drive letters, but also very inconvenient to use |
| Open remote node files with normal permissions | Supported | Not Supported | Not Supported |
| Open remote node files with admin permissions | Supported | Not Supported | Not Supported |
| Remotely locate files in explorer | Supported | Not Supported | Not Supported |
| Remote file download | Supported | Not Supported | Not Supported |
| Remote large file resumable download | HTTP1.1/2/3 all support resumable download | HTTP1.0 does not support resumable download | HTTP1.0 does not support resumable download |
| Quick location to search in a specific folder rather than global search | Supported | Not Supported | Not Supported |
| Real-time engine, any disk changes are synchronized to search system in real time | Supported | Supported | Supported |
| Green single file, no installation required | Supported | Supported | Supported |
File Content Search Comparison with AnyTXT
Timing method: browser request query interface, server waiting response time, all speed tests are non-cached hits
| Test Item | FilePulse 2.0.1 Pro | AnyTXT 1.3.2477 |
|---|---|---|
| 2480 txt files forming novels, building search system | 748 ms (max_batch:500), 2.18 seconds (max_batch:50), larger max_batch means faster speed but higher machine performance requirements | 16.38 seconds |
| Search one word in 2480 files in normal mode without sorting | 2.42 ms | 23 ms |
| Search two words in 2480 files in normal mode without sorting | 2.52 ms | 23 ms |
| Search three words in 2480 files in normal mode without sorting | 2.51 ms | 23 ms |
| Full-text regex matching in 2480 files | 9.03 ms | 90 ms |
| Search one word in 2480 files without sorting with highlighted preview | 2.99 ms | 52.58 ms |
| Search two words in 2480 files without sorting with highlighted preview | 2.75 ms | 49.22 ms |
| Search three words in 2480 files without sorting with highlighted preview | 3.12 ms | 44.28 ms |
| Complex expressions including NOT, AND, OR, left parenthesis, right parenthesis | Full Support | Does not support parenthesis priority |
| Real-time engine, any disk changes are synchronized to search system in real time | Fully real-time system, files that meet conditions are immediately updated to the search system the moment they are saved | Not supported, periodic scanning, cannot update in real time |
| Green single file, no installation required | Completely green, no installation required, ready to use | Requires installation |
| Traverse all files in search system with wildcard content search | Supported, very fast | Supported, but extremely slow |
| Traverse all files in search system with regex content search | Supported, very fast | Supported, but extremely slow |
| Word segmentation normal search | Supported | Supported |
| Word segmentation regex search | Supported | Uncertain, probably not available, no clear documentation of this feature |
| Word segmentation prefix search | Supported | Uncertain, probably not available, no clear documentation of this feature |
| Fuzzy search | Supported | Not Supported |
| Sort by document relevance | Supported | Not Supported |
| Secondary filtering based on file name search results | Full Support | Not supported, only supports coarse-grained folder filtering, folder filtering does not support wildcards or regular expressions |
| Sort by complete file path | Supported | Limited support, sorting becomes very slow when there are many files. |
| Sort by file name | Supported | Limited support, sorting becomes very slow when there are many files. |
| Sort by modification time | Supported | Limited support, sorting becomes very slow when there are many files. |
| Sort by extension | Supported | Limited support, sorting becomes very slow when there are many files. |
Memory Usage Comparison
Memory usage comparison under different scenarios for FilePulse vs competitors
File Content Search Scenario
Compare to AnyTXT file content search functionality
FilePulse indexed 2.27 million filenames across the entire disk and 71,120 Python files for content indexing. FilePulse's final stable memory usage is 264MB with 877MB disk usage. AnyTXT uses 307MB memory with 1.4GB disk usage.
Filename Search Only Scenario
Compare to Everything (since Everything's content search is in early stages)
When content indexing is disabled for filename-only search, FilePulse uses 253MB after stabilizing. Everything uses dual-process mode totaling 246MB memory. Given that FilePulse supports more features, using a few more MB is reasonable.
Download FilePulse
Get started with FilePulse and revolutionize your file searching experience.