Free online tools for images, text, code, and calculations. 100% private — everything runs in your browser.
Image tools: compress, convert, resize, watermark, filters and more.
Text tools: word counter, case converter, diff, encode/decode and more.
Developer tools: JSON formatter, regex tester, JWT decoder, hash generator and more.
Calculator tools: BMI, loan, tip, unit converter, time calculator and more.
Time & date tools: timezone converter, countdown timer, stopwatch and more.
Random tools: coin flip, dice roller, spin wheel, name picker, team generator and more.
Shore.QZZ is a family of six focused web toolkits, each built around a single job. We started it because the tools we reach for every day had become bloated: wrapped in ad walls, hidden behind login screens, and — worst of all — silently uploading our files to a server we had no reason to trust. So we built the tools we actually wanted, and the rule we set from day one is simple: nothing you type, paste, or upload ever leaves your device.
Every tool on this network runs entirely in your browser using JavaScript. There is no backend that receives your images, no database that stores your text, and no account you need to create before a tool will work. Open a page, use it, close the tab. That's the whole product.
When an online tool says it processes your file "in the cloud," it usually means one thing: the file was uploaded to someone else's computer first. For a quick JSON reformat that's harmless — but for a passport photo, a signed contract, or a private document, it's a real risk. Uploaded files can be logged, cached, mined, or leaked in a breach, and you'll never know because you can't audit a server you don't control.
Local processing flips this. The code that does the work is delivered to your browser, and the data never goes the other way. You can verify this yourself: open our tools with your network tab open and you'll see no outbound requests after the page loads. We think that's the only honest way to build a privacy tool — if the work happens on your machine, there's simply nothing for us to leak.
Rather than one enormous "300 tools in one" page that's impossible to navigate, we split everything into six small kits. Here's what each one is actually for:
PicKit handles the image chores that come up constantly when you publish anything online. The tool we use most ourselves is compression: a photo straight out of a phone camera is often 4–8 MB, which is far heavier than any web page needs. Running it through PicKit's compressor — which re-encodes the image and strips the metadata you probably didn't realize was attached (camera model, GPS coordinates, editing history) — routinely gets that down to a few hundred KB with no visible quality loss. It's the single fastest way to make a page load faster.
When to use it: before uploading a product photo to your shop, sending a batch of images by email, or posting to a platform that silently re-compresses everything anyway.
TextKit is for the fiddly text jobs that are too small to open a document editor for. Copying a list out of a spreadsheet and pasting it here to remove duplicate lines, for example, takes five seconds and beats scanning a hundred rows by eye. The case converter fixes the all-caps text that people type in a hurry, and the diff tool shows you exactly what changed between two versions of a paragraph — which we use constantly when reviewing edits.
When to use it: hitting a character limit on a social post, de-duplicating a list of email addresses, or checking whether a copied paragraph actually matches the source.
CodeKit is the kit we built for ourselves. Most of these tools exist as desktop apps or command-line utilities, but when you're mid-debug and just need to prettify a JSON blob or decode a JWT token, opening a terminal feels like overkill. The JWT decoder is a good example: paste a token, and it splits out the header, payload, and signature so you can read the claims without a single line of code. The regex tester shows matches live as you type, which is far faster than the guess-and-check loop in a code editor.
When to use it: reading an API error response, verifying a token's expiry claim, or figuring out the exact color value your designer used.
CalcKit is the everyday-math kit. None of these calculators need a spreadsheet, but some are genuinely error-prone by hand — loan amortization especially. Enter an amount, rate, and term, and the loan calculator shows your monthly payment and the total interest you'll pay over the life of the loan, which is the number most people never see when they sign. The BMI calculator and tip calculator cover the quick checks, and the unit converter handles the unit math that trips everyone up at the worst moment.
When to use it: comparing loan offers before you sign, splitting a dinner bill among friends, or converting units while planning a trip.
TimeKit is built around the one time problem that never gets easier: two people in different cities trying to agree on a meeting time. The timezone converter lets you pick any two cities and see both clocks side by side, so "3pm my time" is no longer a puzzle. The countdown timer is handy for a deadline you can see ticking, and the unix timestamp converter is the quiet hero for developers who keep hitting 1735689600-style numbers in logs.
When to use it: booking a call across the US–Asia split, tracking a launch deadline, or decoding a timestamp in a server log.
RandomKit is for the moments where you need an answer and nobody wants to be the one who decides. The tools here are more useful than they look: the team generator turns a list of names into evenly split groups in one paste, which teachers and event organizers use constantly, and the name picker runs a fair draw for a giveaway without anyone crying foul. The randomness comes from your browser's cryptographically secure generator, not a predictable math formula, so a coin flip here is actually fair.
When to use it: splitting a class into teams, drawing a giveaway winner, or settling a debate where neither side wants to flip the coin themselves.
Most of these tools have a desktop-app or paid-software counterpart that you don't actually need to install. Here's the honest mapping, so you know what you can stop reaching for:
None of these are meant to replace a professional tool for heavy, expert work — a designer still needs a full editor, and a developer still needs a real IDE. These are for the ninety percent of tasks that don't need the heavy artillery.
The kits were built separately, but the real value shows up when you chain them. These are the multi-tool flows we actually use:
Because every tool is a separate page you can open in its own tab, these chains work as a kind of impromptu workflow without any sign-up or a single shared "project" to manage.
A few people have asked whether "runs in your browser" means the tools are limited. The short answer is no — modern browsers are astonishingly capable, and we lean on that:
None of this requires a server, which is exactly the point: the capabilities that used to live on a backend can now live in your browser, and that's what makes a genuinely private tool possible.
We'd rather you not take our word for it. Every browser ships with a way to see exactly what a page sends over the network, and you can use it to confirm that Shore.QZZ tools make no outbound requests after they load:
That silence is the whole point. There is no server waiting for your data, so there's nothing to log, sell, or accidentally leak.
Correct. The tools run in your browser, and your files never leave your device. The only network activity is the initial download of the page itself. You can confirm this with the DevTools method above.
There's no catch. Running a tool in your browser costs us almost nothing per use — there's no server doing heavy work and no database to maintain. That's the same reason the tools stay fast: the "infrastructure" is your own device.
For the reason above, they're safer than a cloud tool — your data isn't transmitted anywhere. The standard caveats still apply: don't use them on a shared or public computer, and close the tab when you're done, since the result stays in your browser's memory until you leave the page.
Anything modern: Chrome, Edge, Firefox, and Safari, on desktop or mobile. A couple of advanced tools use browser APIs that require a reasonably recent version, but any browser updated within the last couple of years will work.
Because processing is local, the limit is your device's memory rather than any server-side cap. On a typical computer, image tools comfortably handle files up to around 50 MB. Very large files on older phones may be slow, but nothing will fail to a server-side error.
Once a page has loaded, yes — the tool itself works without a connection, because there's no server involved in the processing. You do need an initial connection to load the page, but after that, everything runs locally. There's no offline app to install, just load the page and it works.
We tried the single mega-page approach first and it made everything worse: pages got heavy, tools were hard to find, and the search results were muddled because one page was trying to rank for a hundred things. Six small kits with clear names are faster to load, easier to navigate, and easier for you to find in a search. The trade-off is more domains to remember — which is what this hub page is for.
Yes. The tools are free for personal and commercial use, and because nothing is uploaded, there are no licensing or data-residency concerns about "where your files went" — they never went anywhere. The usual disclaimer applies to results: verify anything critical before you rely on it.
Please let us know through the contact page — we fix bugs quickly. That said, the tools are provided as-is and results should be verified for anything important (see our disclaimer). Most "wrong result" reports turn out to be input errors — a unit set wrong, or a number pasted with a stray character — so double-check the input before assuming the math is broken.