Browser-Based Tools That Replace Software You Cannot Install
If your work laptop blocks installations, the browser is still open - and modern browsers handle far more than most people realise. Here are the tasks you can stop looking for software to solve.
Why this comes up
Locked-down laptops are the norm in regulated industries, larger companies, and anywhere with a serious security team. You cannot install software, you may not be able to change settings, and support tickets take a week. Meanwhile the browser has quietly become capable of file handling, image editing, media conversion and hardware access - and none of it requires permission from anyone.
A caveat first: "runs in the browser" does not automatically mean "safe to paste confidential data into". Some of these tools process everything locally in your browser; others upload your file to a server. That distinction matters more than any feature comparison, and we come back to it at the end.
PDF handling
Merging, splitting, rotating and reordering PDF pages is the most common reason people go looking for an installer. It has not needed one for years.
- Your browser already reads PDFs and can print any page to PDF, which is also the simplest way to convert a web page or an email to a file.
- Client-side PDF tools exist that do merging and splitting entirely in JavaScript - no upload, no server. Look for ones that say so explicitly and check whether the page still works with your network disconnected. If it does, nothing left your machine.
- Filling forms works in the browser's built-in viewer on most PDFs.
Images
- Cropping, resizing, rotating, format conversion - all doable with the HTML canvas API, and there are good tools that never upload anything.
- Full editors exist as web apps with layers and filters. They are heavier, but they run in a tab.
- Screenshots need nothing extra: Windows key + Shift + S on Windows, Command + Shift + 4 on macOS.
- Compression before emailing large images works well in-browser, since the encoding happens locally.
Text, code and data
- Diff and compare tools run entirely client-side.
- JSON, XML and SQL formatters - useful, but see the warning below before pasting anything from a production system.
- Regex testers with live match highlighting.
- Base64, URL and hash utilities, all of which are pure computation with no reason to involve a server.
- Markdown editors with live preview and export.
Media
This is the one that surprises people. WebAssembly builds of media tools mean a browser tab can now transcode video and audio locally, at reasonable speed. Trimming a clip, converting a format, or extracting audio no longer needs an install. It is slower than a native application and it will heat your laptop up, but it works and the file never leaves your machine.
Hardware access
Modern browser APIs reach further than most people expect:
- Camera and microphone via getUserMedia - video calls, recording, QR scanning.
- Screen capture via getDisplayMedia - recording your screen without any software.
- Wake Lock API - a page can ask the system to keep the display on. This is what a video player uses.
- WebUSB, WebSerial, WebMIDI - direct device communication, with explicit user permission, in Chromium-based browsers.
- File System Access API - reading and writing local files directly rather than through download folders.
Keeping the machine awake
Which brings us to the reason this site exists. Keeping a computer from sleeping normally means installing a utility - one more thing you are not allowed to do. Two browser-based routes:
The Wake Lock API, which some pages use to request that the display stay on. It works well, but only prevents display sleep, and it does nothing about an idle-triggered lock or a chat status going yellow, because it generates no input.
A browser-based mouse jiggler, which takes a completely different route: display a moving pattern on your phone, rest an optical mouse on it, and the mouse reports genuine movement. Because that is real input, it resets the idle timer and therefore also handles idle locks and presence indicators. Nothing is installed on the computer at all.
The important caveat: local versus uploaded
Return to the distinction from the start, because it is the thing that actually matters when you work with company data.
Some web tools do their processing in your browser with JavaScript or WebAssembly. Your file never leaves the machine. Others upload to a server, process there, and send the result back - which is a data transfer to a third party, and for confidential material that may breach your organisation's policy regardless of how convenient the tool is.
How to tell them apart:
- Read the claim. Local tools tend to say so prominently, because it is their main advantage.
- Test offline. Load the page, disconnect from the network, then use it. If it still works, processing is local.
- Watch the network tab. Open developer tools (F12), go to Network, and use the tool. A large outbound request means your file was uploaded.
- When unsure, treat it as an upload and do not use it for anything confidential.
Applied to this site: the jiggler is drawn locally with a canvas element. It sends nothing about your computer anywhere - and since it has no file input at all, there is nothing it could send. That is the standard worth holding any browser tool to before you paste your employer's data into it.