How the checker works
-
1
Choose a file
Drag a file onto the drop area, or use Choose a File. One file at a time. Your browser reads it on your device.
-
2
Say what it is for
Pick a purpose — a website, an email attachment, a social post, a product listing, print, a job application or a data import. ToolFlect checks the file against the requirements it currently stores for that purpose.
-
3
Read the checks and fix what you can
Every finding is listed with what it means and what to do. Where an existing ToolFlect tool can fix it, you get a direct link to that tool. Where we cannot determine something, we say so instead of guessing.
What gets checked
| File type | What ToolFlect reads | What it cannot tell you |
|---|---|---|
| Images (PNG, JPG, WebP, GIF, BMP, AVIF, HEIC, SVG) | Pixel dimensions, aspect ratio, whether the container declares transparency, and the real format as read from the file header | Embedded DPI metadata is not read, so print sizing is calculated from pixel counts |
| Page count, page sizes, whether a password is required, and whether selectable text exists | Images inside the PDF, colour profiles, and anything on a page that could not be opened | |
| JSON | Whether it parses, the root type, nesting depth, value count and top-level keys | Whether the values mean what your importer expects |
| CSV / TSV | The separator, whether there is a header, row and column counts, inconsistent rows, and decoding problems | Whether specific cell values are correct or in the right columns |
Frequently asked questions
Is my file uploaded anywhere?
No. Your file is read and analyzed by JavaScript running in this browser tab. It is not sent to ToolFlect, and it is not stored. When you remove the file or close the tab, it is gone from memory.
Where do the requirements come from?
They are the rules ToolFlect currently stores for each purpose. They are guidance, not a guarantee, and they are not official statements from any platform. You can read exactly what each check looks for in the results list.
Why does a check say it could not be determined?
Because the browser genuinely could not read that property. Rather than guess, ToolFlect reports it as unknown and tells you why — for example, if the PDF reader library could not be loaded, or if a format does not record transparency. An unknown result is never counted against your file.
Does this check whether a platform will accept my file?
No, and it does not claim to. It checks whether your file meets the requirements ToolFlect stores. Always confirm the final requirements with the platform or service you are submitting to.
Privacy: your file stays in your browser
This checker runs entirely on your device. Your file is analyzed locally in your browser and is not uploaded. Nothing about your file — its contents, its name or its metadata — is sent to ToolFlect or to anyone else.
- No upload, no account, no sign-up
- Your file is never written to storage; it is discarded when you remove it or close the tab. The only thing stored locally is your analytics choice, if you make one
- One library (used to read PDFs) is loaded on demand from a public CDN when you check a PDF — that request fetches the library only, never your file
- Google Analytics counts visits without cookies until you accept analytics, and it never receives your file, its name or its metadata
- You can verify it yourself: open your browser's developer tools, switch to the Network tab, and check a file — no request carries your file