Edit text in place, sign, redact, reorganize. True content-stream rewrite, not stamp-on-top.
LaunchEdit, sign, redact, and reorganize PDF files in your browser. The Adobe Acrobat alternative that runs on your device — no upload, no subscription.
Pixel-perfect PDF diff with word-level text view, metadata + form-field compare, ruler, and exclusion zones.
LaunchSide-by-side or overlay PDF diff with a document-type selector — Document (contracts, reports), AEC / Blueprint (drawings, schematics), or Image-Scan. Highlights pixel-level differences plus a word-level text diff in a modal.
Open any PCB Gerber bundle in your browser. Gerber X2, Excellon, layer compare, snap-to-pad measure, snapshot URLs.
LaunchOpen RS-274X / X2 Gerber and Excellon files. Inspect layers, measure traces, export to PNG / SVG / DXF.
Compress, merge, split, convert, and manipulate PDF files.
Resize, compress, convert, and transform images.
Format, encode, decode, and validate code and data — safe for production secrets.
Convert, compress, and cut audio and video — MP3, WAV, MP4, WebM, Opus — all in your browser, nothing uploads.
Sourdough baker math, canning processing times — kitchen math you should not memorize.
AES-256 file encryption and self-destructing encrypted notes.
Analyze packet captures and run sysadmin diagnostics in your browser — nothing uploads. PCAP Analyzer ships first.
Chart-overlay technical analysis and precision financial math — your screenshots and numbers never leave your device.
Open CAD, BIM, medical, and enterprise files without paying $300-30K/year for the native software. Gerber Viewer ships first.
Loft Tools runs in the browser on every modern phone — iPhone Safari, Android Chrome, Samsung Internet — without anything to install from an app store. The mechanics, the memory limits to be aware of, and how to add an icon to your home screen if you want one.
Yes — Loft Tools runs in the browser on every phone made in the last five years. Same URL, same code, same tool list. iPhone Safari, Android Chrome, Samsung Internet, Firefox mobile, Brave mobile. No app store, no install dialog, no per-platform binary. The file-processing operations that used to need a desktop are within reach of the device already in your pocket.
(Also tested on a Kindle Fire’s underpowered Silk browser. Slow but works. Yes, that’s how I spent one weekend.)
Most of the catalogue. Specifically:
Tools that run a heavy ML model the first time you open them work on phones but the model download is bigger. PaddleOCR for non-English OCR downloads ~10–15 MB per language on first use, cached after. The Premium background-removal model for ID photos is larger (~115 MB) and only downloads if you enable that feature — it is strictly opt-in.
Open Safari, type the URL, you’re using the tool. The browser downloads the page code on first visit (one-time cost of a few MB), the service worker registers, and subsequent visits use the cached code. Drop a file from Files.app, Photos, or any share sheet that hands files to Safari — the file is read into the tab’s memory, the tool runs, the result downloads via the browser’s normal download flow. iOS handles the file save through the share sheet, so you can send the result to Files, AirDrop, Messages, or anywhere else.
There is one iOS-specific limit to know about: Safari enforces a per-tab memory cap — low hundreds of MB on modern phones. Big PDFs (a few hundred pages with images), large videos, or 4K image batches will hit the ceiling before they hit a desktop ceiling. We surface a warning when we can detect a file is likely to push past the limit. For routine work — the contract you need to sign, the boarding pass you need to crop, the recipe scan you want to deskew — the ceiling rarely matters.
Identical, with more memory headroom. Android Chrome’s per-tab memory ceiling is higher than iOS Safari’s, and devices with 6+ GB of RAM generally process larger files without issue. The file picker integration is also better — most Android phones can hand any file in storage straight into a browser-side tool.
If you’d rather have an icon on your home screen, you can install the site as a Progressive Web App from Chrome’s menu. PWA install gives you a launcher icon and a standalone window (no browser chrome visible) while keeping the same browser-tab mechanics underneath. Nothing about the file-handling changes — it’s still the same code running locally.
Same as iPhone, with the desktop-class Safari memory profile if you’ve got an M-series iPad or recent iPad Pro. Drop in a file from Files or from a share sheet, work on it, download the result. The wider screen also means tool UIs that are tight on phones — like compare-pdf with its dual-pane view — work comfortably.
Worth noting: Loft Tools is one of the few browser-based PDF stacks that runs at full feature parity on iPad. Some heavier tools assume desktop only and ship a stripped iPad version, or none at all (Bluebeam Revu ended their iPad app on December 31, 2025). If you do PDF work on iPad as your daily driver, browser-based is increasingly the only option that still actively ships features.
A common assumption is that mobile tools must phone home more because “the browser is more limited.” The opposite is true. Mobile browsers run the same JavaScript and the same WebAssembly that desktop browsers run. The same five-step verification flow from the devtools walkthrough works on mobile too — though the DevTools experience is harder (iOS requires Safari’s “Web Inspector” mode connected to a Mac).
The architecture guarantees apply equally: file in browser tab, no upload endpoint, no third-party file sink. The pillar on /docs/how-it-works/ covers this in full.
We get this question. A native iOS or Android app would give us: better memory headroom (no per-tab cap), background processing, deeper file-system integration, push notifications, app-store discoverability. It would also require: maintaining two more codebases (Swift + Kotlin), going through app-store review every change, paying platform fees, losing the “one URL, all platforms” property, and losing the “no install” property that’s a feature for many users.
The tradeoff hasn’t tipped for us. The browser is good enough for the work we do, and good enough is the bar that matters here. If a specific workflow genuinely needs the native-app advantages, that’s the right tool for that workflow — not Loft.
Anything running iOS 16+ or a recent Chrome/Edge/Firefox on Android gets full feature support. iOS 15 and Android 10 are still mostly functional; older than that and the WebAssembly support gets shaky.
Yes, if you’ve visited the tool while online first. The service worker caches the code; subsequent offline visits use the cache. Pinned tools are deliberately set up to work offline. See the pillar section 3 for the mechanics.
Yes via PWA. On Android Chrome: tap the menu, “Install app”. On iOS Safari: tap the share icon, “Add to Home Screen”. The result is an icon on your home screen that launches in a standalone window without the browser address bar.
The first-visit code load is a few megabytes total, similar to a single webpage with images. After that, cached. PWA install adds a launcher icon but doesn’t materially increase storage use beyond the already-cached code.
The pillar at /docs/how-it-works/ covers the cross-platform model in section 8, and the memory ceiling in section 8’s honest-limits paragraph. The changelog tracks the mobile-specific polish work that keeps phones at parity.
