How Local File Processing Works

Selected files are opened through browser file APIs, normalized into an in-memory virtual filesystem, and processed by local JavaScript workers. There is no file-processing API or database.

Local Files

↓

Browser File APIs

↓

Local Worker Pool

↓

File Detection

↓

Archive / Document Extraction

↓

Local Search / Diff / Analysis

↓

Results in Browser

Your file contents×never sent to a remote file-processing server

Virtual paths, not physical paths

Archive entries use virtual locators such as backup.zip!/project/config.yaml. The application does not claim those are physical operating-system paths.

Progressive local work

Files become searchable as they are read and extracted. Search, diff, hashing and lexical similarity operations run in cancellable Web Workers. Archive and document extraction is local and bounded by safety limits.