Questions, answered.

Yes, completely. There are no tiers, no day limits, no premium features hidden behind a paywall. Every tool works fully every time you use it. The site is supported by advertising — when you use Hoja, you may see an ad. That's the trade-off, and we think it's a fair one.

No. There are no accounts on Hoja. You open the tool, drop your file, and it works. We don't ask for your email address, we don't set a password, and we have no login screen. The absence of accounts is not a missing feature — it's a deliberate choice that makes the privacy guarantee easier to keep.

Through advertising. When you visit Hoja, you may see ads displayed by Google AdSense. We don't sell your data, don't run sponsored content disguised as tools, and don't have an enterprise tier we're trying to upsell you toward. If the ads bother you, an ad blocker works fine — the tools function whether ads are visible or not.

Hoja was built by a solo developer based in Bengaluru, India. It started as a frustration with how most PDF tools treat users — as funnel targets rather than people with a simple task to complete. There's no team, no investors, and no growth playbook. If something's broken, reach out — it'll actually get fixed.

No. Every tool on Hoja runs entirely in your browser using the Web File API and JavaScript libraries. When you drop a file onto a tool, your browser reads it into local memory. All processing happens on your device. The output file is generated in memory and downloaded directly — no data ever leaves your machine. You can verify this yourself by watching your browser's network tab while using any tool.

No. Because your files never leave your browser, we have no technical means to see their contents. We don't see filenames, page counts, or any other metadata from your documents. There is no server receiving your files, so there is nothing to log, store, or access. This is not a policy — it's an architectural fact.

We use Cloudflare Web Analytics for basic usage statistics — it's cookieless and doesn't track individual users. Google AdSense may set cookies for ad personalisation. We don't use analytics cookies of our own, and we don't run any cross-site tracking scripts. You can find the full breakdown in our privacy policy.

For documents with sensitive content — contracts, financial records, medical files — the local-processing model is genuinely safer than upload-based services. Your file never leaves your device, so there's no server-side breach to worry about, no upload interception, and no third-party storage. The remaining risk is the security of your own machine. As with any browser-based tool, make sure you're on a trusted device and network before working with highly sensitive material.

There's no server-imposed file size limit. The practical limit is your browser's available memory. Most modern devices handle files up to a few hundred megabytes without issue. Very large files (500 MB+) may cause slowdowns depending on your device. If a file is too large to process, your browser will slow down or the tab may become unresponsive — in which case, try closing other tabs to free up memory.

Yes. The site is designed to work on mobile browsers. File picking works via your device's native file picker. Processing speed on mobile depends on your device — newer phones handle large files easily, older ones may be slower. For heavy-duty work (large file batches, high-resolution PDF-to-image conversion) a desktop browser will generally be faster.

Partially. Once the page has fully loaded in your browser, most of the processing libraries are cached and will work even if you lose your connection. However, fonts loaded from Google Fonts and ads from Google AdSense require a connection. The core tool functionality — file processing and download — works offline once the page is loaded.

All modern browsers: Chrome, Firefox, Safari, Edge, and Brave work well. We recommend Chrome or Edge for the best performance, especially for the PDF-to-JPG tool which uses canvas rendering. Internet Explorer is not supported — it's been discontinued since 2022 and lacks the APIs the tools require.

Hoja's compression works by re-encoding embedded JPEG images at a lower quality and smaller maximum dimension. If your PDF was originally created from text (a Word document, a spreadsheet export, a web page print), it contains very little image data — most of the file is fonts and vector instructions, which can't be compressed this way. In those cases, gains will be minimal. The tool works best on scanned documents or image-heavy PDFs. It will always tell you honestly how much it was able to reduce the file.

The PDF to JPG tool uses PDF.js (pdfjs-dist), a heavier rendering library than the pdf-lib we use for other tools. On first load, the browser needs to download and initialise the PDF.js worker, which takes a few extra seconds. Subsequent visits are faster because the worker is cached. This is a one-time loading cost, not a per-file cost.

Not directly — the tools are built for interactive use in a browser, not as a library or API. However, the underlying open-source libraries we use (pdf-lib, PDF.js, mammoth.js) are all available on npm and can be integrated into your own project. They're well-documented and actively maintained. If you're building something that needs PDF processing in the browser, those are the libraries to start with.