Modern browser requirements
NoblePDF is a substantial browser application, not a static PDF viewer. Current tools use technologies such as WebAssembly, Web Workers, Canvas, Blob downloads, IndexedDB and modern JavaScript. A current Chromium-based browser is the primary release-test target, while current Firefox and Safari-family browsers may work where they support the same required APIs. Keeping a browser updated is particularly important for PDF and WebAssembly security fixes.
Desktop versus touch
The full editor has dedicated desktop and touch-oriented layouts. NoblePDF routes users using browser/device signals such as user agent and touch capability, while still supporting direct loading of the appropriate editor page. The responsive test suite includes desktop widths, phones and tablet-style viewports because a layout that works at 1920 pixels can still fail in iPad Split View or on a narrow phone.
Memory and large documents
Local processing means your device supplies the memory and CPU. A small text PDF is inexpensive; a scanned 300-page document can require hundreds of rendered images and substantial OCR work. If a browser tab is terminated for memory pressure, splitting the document into smaller parts can be more reliable than repeatedly retrying the full file. Closing other memory-heavy tabs can also help on mobile devices.
Downloads and browser permissions
NoblePDF creates results as browser downloads. Some browsers may ask permission for repeated downloads, especially when a workflow creates multiple files or a ZIP. Private-browsing modes can also place tighter limits on persistent storage. If the full editor cannot retain a project between sessions, check whether the browser is configured to clear site data automatically.
Offline behaviour
The current runtime is self-hosted, which removes dependence on public CDNs, but NoblePDF is still delivered as a website. Once an editor page and all required assets are loaded, many document operations do not need a remote processing service. This is not the same as promising a fully installed offline desktop application; browser caching rules and first-load availability still matter.
HTML-to-PDF external resources
Most NoblePDF document tools are designed not to require external content. HTML conversion is unusual because the source itself may reference remote images, fonts or styles. External loading is opt-in. When enabled, browser CORS rules, network availability and the remote server’s policies can affect how the converted page looks.
Troubleshooting
- Reload the page if a required local runtime asset failed to load.
- Try a current browser version before reporting a rendering problem.
- For very large scanned PDFs, test a smaller range first.
- Do not disable JavaScript or WebAssembly for the NoblePDF origin if you want the editor to function.
- If the issue persists, use the Contact page and describe the browser, operating system, tool and visible error message.
Minimum browser baseline
NoblePDF targets current browsers with WebAssembly and modern security-policy support. As a practical baseline, use Chrome 97 or later, Firefox 102 or later, Safari 16 or later, or a current Chromium-based Edge release. Newer versions are strongly recommended.