Private — processed on your device, never uploaded
Prepare a set of files to requirements
Prepare a set of files to size and format rules, and check them.
What the form asks for
Type in the requirements you were given. Toolpit checks what it produces against these numbers and nothing else — it has no list of institutions, and it cannot tell you whether a form will accept your file.
About this tool
Application forms ask for a photo at exact pixels, a signature under some number of KB, and a scan in one particular format — and getting all three right usually means four tools and a lot of guessing. Enter the requirements once, map your files to them, and Toolpit prepares each one and then reads the finished file back to check it actually meets what you typed. It tells you what it could not verify instead of pretending. Nothing is uploaded.
Private by design — your files never leave your device. Toolpit has no upload step and no server that can see your document — the work happens in this tab, on your machine, and stops the moment you close it.
How to prepare a set of files to requirements
Name each file the form asks for — photo, signature, certificate — and enter the format, pixel size and size limit it specifies.
If the limit just says KB, check whether the form means 1,000 or 1,024 bytes. Both are offered, and near the limit the choice decides whether your file is accepted.
Choose a file for each one, then click Prepare. Originals are never modified.
Read the result for each file: what was required, what the finished file actually measures, and anything the transformation cost.
Open the prepared files and look at them before you send them. A file that meets every number can still be unusable.
Questions
Are my files uploaded anywhere?
No. There is no upload step and no server that could receive the file — the tool runs as code in this browser tab, works on the copy your browser opened, and forgets it when you close the tab. You can check this yourself: open your browser’s network panel and run the tool. You will see the page, its scripts and the ads that pay for the site — and no request carrying your file, because there is no endpoint to carry it to.
Is 200 KB the same as 200 KiB?
No, and the difference is 4,800 bytes — enough to fail. KB properly means 1,000 bytes, so 200 KB is 200,000. KiB means 1,024, so 200 KiB is 204,800. Many upload forms say KB and enforce KiB. Both units are offered here, and if your finished file lands between the two readings the result says so explicitly rather than picking one and hoping.
Will it shrink the picture to get under the size limit?
No. If you asked for exact pixel dimensions, those are kept and the size limit is approached by compression alone. Quietly resizing past a stated dimension is the usual way a tool turns every check green and gets the file rejected by the form anyway. If no quality setting fits the limit at those dimensions, you get the smallest honest attempt, a failing size check and the number of bytes it is over by — so you can raise the limit, loosen the dimensions, or decide the two rules conflict.
What does "not checked" mean next to a result?
That the tool could not establish that property from the finished file, so it is refusing to claim it passed. The usual cause is a format whose dimensions it cannot read back from the header. It is deliberately not drawn as a tick: a check you cannot perform and a check that succeeded are different things, and showing them the same way is how verification tools become useless.
Does passing these checks mean my application will be accepted?
No, and nothing here should be read that way. The checks cover the numbers you typed in — format, pixel size, file size — measured on the file that was produced. Toolpit has no list of institutions and no knowledge of what any form requires. Whether a photo is framed correctly, a scan is legible, or a document is the right one is yours to judge, and whether it is accepted is the organisation’s.
What happens if one file fails?
The rest are still prepared. A pack where one file cannot be opened gives you every other file, with that one marked and the reason shown. Nothing is silently dropped and the pack is never reported complete when part of it is not — which would be the worst possible failure for a tool whose job is checking.
Can I save these requirements and reuse them?
Not on the website, where everything is manual and free. Saving a set of requirements as a recipe and re-running it on a new set of files is the one paid feature in the mobile app, and it is not built yet. Preparing and checking files by hand stays free everywhere.
Related tools
Every one of these runs in your browser too — no upload, no signup, no watermark.