Frequently Asked Questions

Yes. All Phase 1 tools are free to use without an account. We cover hosting and development costs through Google AdSense advertising shown on the site. There is no paywall, no usage cap, and no "premium" tier locking the core features.

No. All processing happens entirely inside your browser using JavaScript and WebAssembly. Files you select are read into memory in your browser, processed there, and the result is given back to you for download. We do not have any server-side upload endpoint for tool files. You can verify this in your browser's DevTools Network tab — you will not see any of your file content being sent. See How It Works for architecture details.

There is no hard server-side limit because we do not upload files. The practical limit is your device's available memory. As a guideline: PDFs up to a few hundred MB and images up to ~50 MB usually work on a typical laptop. Mobile browsers have tighter memory budgets — a banner inside the tool will warn you when memory pressure is high. If a very large file fails, try splitting it first or run it on a desktop browser.

We support the current and previous major versions of Chrome, Edge, Firefox and Safari, on both desktop and mobile. The tools rely on standard Web APIs (Web Workers, WebAssembly, Canvas, File API). Internet Explorer is not supported.

Partially. AinnoBox is a Progressive Web App (PWA), which means once you have visited the site, the core HTML, JavaScript and WASM modules can be cached. You can then re-open most tools without an internet connection. First visit still requires network. Adding the site to your home screen gives the closest-to-native experience.

No. There is no sign-up, no login form, no email collection. Open a tool, drop your file in, get the result. We do not run any user database.

Browser-based processing has overhead: the file is read into memory, the WASM runtime initialises on first use, and Web Workers handle the heavy work off the main thread. For everyday tasks (compress, merge, resize) the difference is negligible. For very large batches or extreme compression ratios, a native desktop tool may still be faster. We pick the best library available in the browser for each task — for example, Squoosh WASM codecs for image compression, pdf-lib for PDF manipulation, pdf.js for rendering.

We do not log file content, file names or contents-derived metadata, because no file content is sent to our servers. We collect aggregate, anonymous traffic stats via Plausible Analytics (page views, referrer, country at country level, browser family) — strictly to understand which tools are used. Plausible is cookie-less and does not build cross-site profiles. Details: Privacy Policy.

We use Google AdSense to display ads. AdSense may use cookies and similar technologies to measure ad performance and to personalise ads in regions where that is allowed. In jurisdictions covered by GDPR/UK GDPR/CCPA you will see a consent banner the first time you visit; you can refuse personalised ads, in which case non-personalised ads are shown instead. To learn more or to manage your ad preferences, see Google's ad policies and our Privacy Policy.

No. We do not see your files and we make no claim on them. The files you process remain yours, with the same rights you had before processing.

On first use, the tool downloads its WebAssembly module (typically a few hundred KB to a few MB) and initialises the runtime. Subsequent opens are nearly instant because the module is cached by your browser.

The tools themselves do not need cookies. The site stores a small amount of state in your browser's localStorage (theme, language, ad consent choice). The cookies that may be set come from Google AdSense (for ad measurement, and ad personalisation if you opted in). All of this is described in our Privacy Policy.

Email contact-us@ainnotech.com.au with as much detail as possible: browser, operating system, the tool you used, and steps to reproduce. Please do not attach files containing sensitive information — describe the issue in text instead. See the Contact page for other types of inquiries.

Phase 1 covers core PDF and image manipulation. PDF password protection / unlock require AES encryption that pdf-lib does not yet implement; we removed those tools rather than ship a half-working version. They are planned for Phase 2 with a proper crypto library. OCR and PDF form filling are also on the roadmap.

Three ways: (1) Open your browser's DevTools, switch to the Network tab, then run a tool — you will not see any of your file content being uploaded. (2) Disconnect from the internet (e.g. airplane mode) after the page has loaded; the tools continue to work. (3) Read our strict Content Security Policy headers, which limit script sources and where data can be sent. The architecture is described on the How It Works page.