Local processing means the browser on your device reads and transforms a selected file instead of first sending it to a remote processing server. The website can still download the code needed for that work and make ordinary website requests. Local file processing describes where the operation happens; it does not mean the whole website is disconnected from the internet.
Local processing vs server processing
| Question | Local processing | Server processing |
|---|---|---|
| Who reads and transforms the file? | Software running on your device. | Software on a remote server after an upload. |
| Whose resources do the work? | Your device’s processor and memory. | Primarily the server’s processor and memory. |
| What needs a connection? | The page and any uncached code, models, or other requests. | Uploading the input, processing requests, and receiving the result. |
| What should you check? | Actual upload behavior, other requests, and local storage. | Upload handling, retention, access, and deletion policies. |
For example, rotating a PDF locally lets your browser create the rotated copy from the selected original. A server-based service receives the PDF, creates a copy remotely, and sends the result back. Either approach can have additional features; the label alone does not describe every data flow.
What happens when you select a file?
A browser file picker gives the page access to the files you choose. Selection and upload are separate actions: JavaScript can read the selected bytes locally, but a website can also send those bytes over the network. A button labeled “Choose file” does not establish which behavior follows.
Processing may hold input bytes, decoded images, page previews, and output bytes in memory at the same time. A temporary object URL, usually starting with blob:, lets the page display or download browser-held data. Creating that URL is not an upload or a public sharing link. Releasing it lets the browser reclaim associated resources; it is not a promise of secure erasure from device memory or storage.
Why does a local tool still download things or use memory?
JavaScript runs application logic. WebAssembly lets browsers run compiled processing engines, while browser features can decode images and draw previews. None of these technologies automatically prevents a website from making network requests.
A tool may need to download a reusable OCR language file or a background-removal model before it can work. Receiving that shared resource is different from sending your document to a server. The processing itself still consumes CPU and RAM: a compressed photo can expand into a much larger pixel buffer, and a long PDF may need many page previews. Large jobs can be slow or exceed a phone’s available memory.
What does “offline after first load” depend on?
Offline use depends on the exact page, processing engine, and required resources being available in the browser cache. Opening a homepage once does not necessarily cache every tool. Browsers may clear cached data, private browsing may retain less, and a different language or model may need a fresh download. Test the specific workflow offline before depending on it.
What local processing does not guarantee
- It does not prove that a site has no analytics, cookies, contact services, or other network traffic.
- It does not remove metadata or visible personal information from the output.
- It does not protect a downloaded file from other people or software with access to your device.
- It does not eliminate risks from browser extensions, compromised code, or an insecure device.
Check a service’s current privacy disclosures and the behavior of the particular tool. If you plan to share the result, also review file metadata and visible content.
How SoraFiles uses local processing
SoraFiles processes supported files in the browser and does not send their contents or results to a SoraFiles processing server. Its Privacy page separately describes website requests and anonymous tool-usage events. The contact form is an intentional exception to general website use: information you submit there is sent to the contact service.
The Open Source page identifies the browser libraries and application source. These are first-party implementation disclosures, not an independent security certification. Try a representative workflow such as Compress PDF or Image Converter, or browse All Tools.