Nothing to clean up — it was never sent anywhere. Closing the tab clears it from memory, same as any other unsaved browser data.

Yes, once the page and its libraries have loaded once in a given session. There's no per-conversion network call.

Scanned PDFs — photos of pages, with no embedded text layer — have nothing for this tool to read. That's a job for OCR, and OCR is a job for a model, which is the one dependency we're avoiding here.

This removes protection, it doesn't crack it — you need to already know the password, or the PDF needs none to open (just restricted permissions).

The output has no open password and none of the original printing, copying, or editing restrictions. Anyone with the file can use it freely, so only unlock files you're allowed to share that way.

It covers standard PDF encryption — RC4 and AES, 40- to 256-bit, which is what the vast majority of "protected" PDFs use. Third-party DRM systems are a different, much rarer thing, and aren't covered.

Rough published tank sizes and consumption figures for common models sold in Malaysia and Singapore. Your actual car may vary slightly — the manual capacity field is always there if the preset doesn't match.

No — nothing is written to disk or sent anywhere. Refresh the page and it's back to the defaults, same as every other tool here.

Made this over teh tarik levels of confidence, not a calibrated fuel sensor — dashboard needles lie a little, pump prices shift with the wind, and your actual fill-up may vary by a litre or two. Treat it as a friendly estimate to plan your trip to the pump, not the absolute truth. Drive safe, fill up before the light blinks red, and lambat sikit takpe, yang penting selamat.

Not quite — this is a structural and checksum check, not a full bit-exact decode against the file's internal MD5 signature (that needs a real FLAC decoder). It's very good at catching the kinds of damage that actually happen — bad transfers, bit rot, dropped bytes, truncation — but "Verified" means the file's structure and checksums are clean, not a guarantee equivalent to a full decode.

This tool flags likely corruption based on FLAC's own checksums and structure — a solid first pass for spotting bad rips, bad transfers, or bit rot, not an official mastering-grade audit. If a file gets flagged, it's worth a listen before you delete anything.

Yes — every check above runs in memory, in this tab. Nothing is uploaded, logged, or stored anywhere; close the tab and it's gone, the same way it arrived.

Probably close, not exact. Real EPF and SOCSO contributions are read off official wage-bracket tables rather than a flat percentage, and PCB/MTD has more relief categories than shown here. Treat this as a solid estimate for planning, not your final number.

No — every figure stays in this browser tab and is recalculated locally. Refresh the page and it's gone, same as every other tool here.

This calculator assumes resident tax treatment. Non-residents are taxed differently (a flat rate, with no personal reliefs) — this tool won't give you a useful number in that case.

SHA-256 or SHA-512 if the publisher offers them — MD5 and SHA-1 are still fine for catching accidental corruption, but both have known collision weaknesses, so don't lean on them where someone might be deliberately trying to fake a match.

Different sites publish different algorithms — having all four ready means you can paste whichever one you were given without guessing first.

Yes, though very large files take longer since everything runs on your device's own CPU — there's no server doing the work in the background.

Most phones tag every photo with the exact location it was taken, by default. Handy for sorting your own library, less handy when you post the original file somewhere public.

Not yet — only JPEG is supported right now, since it's by far the most common format for carrying EXIF GPS data. Anything else is skipped rather than silently left untouched.

No — only the metadata segments are removed. The compressed image data itself is copied through exactly as it was, so there's no quality loss from this process.

The page itself, and one small helper library, need to load once. After that, every code you generate or read is handled entirely on your device — nothing is sent anywhere.

It controls how much of the code can be damaged, smudged, or covered (like with a logo) and still scan correctly. Higher levels are more forgiving but make a slightly denser code.

Usually it's a blurry photo, a code shot at too steep an angle, or an image that doesn't actually contain a QR code. Try a straighter, better-lit shot, cropped closer to the code itself.

Usually an interrupted download or transfer, a flaky USB drive, or a cloud sync that didn't quite finish. The archive can look complete — right file size and everything — while a chunk in the middle is silently wrong.

No — this only tells you which files are affected, so you know whether to re-download, re-copy, or re-request the archive rather than finding out the hard way mid-extraction.

It means that specific entry uses a compression method or archive feature this tool doesn't decode (like Zip64 or an uncommon method) — it isn't a sign the file is broken, just that it wasn't verified.

No. Every entry stays in this browser's local storage on this device. There's no account, no server, and no sync — which also means it won't show up if you open Robok on another device.

Your logged expenses will be erased along with it, the same as any other site's local data. Export to CSV beforehand if you want to keep a copy.

Not yet — this version is focused purely on tracking where money goes out. Pair it with the Payslip Calculator to see the income side of the picture.

It runs the same reads a fingerprinting script would, but the result is shown only to you, in this tab, and thrown away the moment you leave the page. Nothing is sent, logged, or stored — that's the entire point.

Because the signature is built from real differences between browsers and devices — different font sets, different GPUs, different rendering engines. That's exactly why it works as a fingerprint in the first place.

Browsers with built-in fingerprint resistance (like Firefox's strict mode, Brave, or Safari's private browsing) deliberately blur or standardise several of the signals shown here. This page won't fix that for you — it just shows you what's currently exposed.