Randomly.online Reviews and Details

Questions & Answers

1. How would you describe the primary audience of Randomly.online?

   Anyone with a file and a deadline, which in practice splits four ways. Students and office workers doing one-off jobs: merge these six PDFs, get this photo under 2 MB, work out how many business days there are until the 30th. They arrive from a search, use one tool, and leave.

   Developers and technical people who want a formatter, a JWT decoder, a regex tester or a hash without pasting company data into a site they have never heard of. That group cares most about the no-upload property and is the most likely to go and check it.Writers and marketers in the text and SEO tools: word counts, readability, case conversion, meta tags, schema and sitemaps.

   Teachers, freelancers and small business owners in the calculators. Loans, tax, a spreadsheet to convert, grades to work out. What they have in common is that none of them want to make an account to do a two-minute task.

2. What makes Randomly.online unique?

   No file leaves your device. Every one of the 400-plus tools does its work inside the browser tab you already have open, using JavaScript and WebAssembly, so a PDF you merge or a photo you compress is read and written on your own machine. There is no server that could receive it. That is checkable rather than promised: no tool page uses FormData or XMLHttpRequest, and a committed script, verify-no-upload-apis.mjs, fails the build if one ever appears.

   The second thing is breadth in one place. Ten categories, from PDF and image editing through calculators, date and time arithmetic, unit conversion, developer utilities and spreadsheet readers, all with the same interface and none of them behind a sign-up.

3. Why should a person choose Randomly.online over its competitors?

   Three things, and each is a limit other tool sites impose that this one cannot. There is no upload, so there is no file size cap, no queue and no daily allowance. The constraint is your own machine, not somebody's free tier. Nothing is watermarked. Nothing expires after an hour.

   There is no account. No email, no password, no verification step between you and a tool you needed for ten seconds. The work stays private by construction, not by policy. Policies change. A tool that makes no network call cannot send your document anywhere, even if someone wanted it to. Contracts, payslips, medical scans: that is where the difference stops being theoretical.

4. What's the story behind Randomly.online?

   It started with a habit I did not like: uploading a private file to a stranger's server to do something trivial to it. A contract to compress. A payslip to convert. The tool worked, and the file was now sitting on somebody else's machine with no way to know for how long. I am Dhruba Singha Roy. Before this I built Animetype, a social app that reached 35,000 downloads on the Play Store, and led a Google Developer Student Club of more than 1,000 members at Haldia Institute of Technology. Randomly.online began as a handful of tools that did the job in the browser instead. Browsers can do far more than people assume. That was the surprise. WebAssembly runs OCR and SQLite, canvas handles the image work, and pdf-lib rewrites a PDF with no backend at all. Once that was clear, the question stopped being whether a tool could avoid the server and became how many could. It is past 400 now, across ten categories, and not one of them has a server doing the work. Everything is free. There is no paid tier planned and no advertising.

5. Which are the primary technologies used for building Randomly.online?

   Deliberately plain on the outside and specific underneath. The site is static. No frontend framework, anywhere: hand-written HTML, CSS and vanilla JavaScript. One subsystem, the date and time tools, is written in TypeScript and compiled with Vite. Bundling, where it is needed, is esbuild. The work itself is done by the browser. Canvas and the File API handle image editing. PDFs go through pdf-lib for writing, pdf.js for rendering, and jsPDF with html2pdf.js for export. Spreadsheets are read by SheetJS, archives by JSZip. WebAssembly does the heavy parts: Tesseract for OCR, SQLite compiled to wasm for the SQL playground, MediaPipe for vision. Motion drives the animation. The main libraries are vendored into the site under assets/vendor rather than fetched at run time, so a tool does not stop working because a third party had a bad day. It installs as a progressive web app, with a service worker for the shell. Hosting is Cloudflare Pages. Static files, no origin server.