MZTechPro uses different technical approaches depending on what a tool needs to do. This page explains what we mean by Local Processing, what happens to files on supported tools, and what local processing does—and does not—mean.
What “Local Processing” Means
When an MZTechPro tool is specifically marked Local Processing, the selected file is processed by code running in your web browser rather than intentionally sent to an MZTechPro file-processing server.
1. You select a file
Your browser receives access to the file you choose through the file picker or drag-and-drop area.
2. The browser processes it
Supported tools may use browser technologies such as JavaScript, Canvas, Web APIs, or in-browser libraries to perform the task.
3. A result is created
The processed output is generated in the browser's memory or temporary browser context.
4. You download the result
The finished file is saved through your browser to the location you choose on your device.
Does Local Processing Mean the Webpage Makes No Network Requests?
No. A webpage can still communicate with the internet while the selected file itself is processed locally. For example, a page may request:
- HTML, CSS, JavaScript, fonts, icons, or other page assets.
- Third-party libraries required to display or operate a feature.
- Analytics, consent-management, security, or advertising services if enabled.
- Normal navigation or API requests unrelated to the content of the selected file.
Therefore, the term Local Processing refers specifically to the processing path of the selected file, not to every network request made by the webpage.
Does MZTechPro Store Files From Local Processing Tools?
If the selected file is not intentionally uploaded to MZTechPro for processing, MZTechPro does not receive that file through a file-processing upload and therefore does not have a server copy to retain through that workflow.
How Can I Tell Which Processing Method a Tool Uses?
Look for processing information on the individual tool page. Tools that use local processing should state it clearly. If a future feature requires server-side or another type of processing, the page should describe that method instead of relying on a site-wide assumption.
| Label | What it means |
|---|---|
| Local Processing | The selected file is processed in the browser rather than intentionally uploaded to MZTechPro for file processing. |
| Processing method stated on page | The tool page explains the relevant workflow or any important exception. |
| No processing label | Do not assume a particular privacy model. Review the page description before using the tool for sensitive material. |
Third-Party Libraries
Some browser-based functionality may rely on third-party open-source libraries or externally hosted resources. Loading a library is not the same as uploading the selected file, but users handling highly sensitive material should always consider their own security requirements, browser configuration, extensions, and network environment.
Sensitive and Confidential Files
Browser-based processing can reduce unnecessary file transfers on supported tools, but no online webpage should be treated as a substitute for an organization's approved security process.
Browser and Device Limitations
Local processing uses your own device resources. Very large files or large batches can require significant memory and CPU power. Individual tool pages may therefore set practical file, page, or batch limits.
Read the full Privacy Policy
This page explains file-processing behavior. Our Privacy Policy covers website data, cookies, analytics, advertising, and other privacy matters.
Privacy Policy