File checker

See what a file really is before you upload it: its real type, exact size, pixel size or page count, and hidden details such as where a photo was taken. Check it against a form’s requirement, and remove photo metadata without losing quality.

Check against a form’s requirement Optional

Enter only what the form states. Every file gets a pass or fail table for these rules.

Allowed formats
The pixel size must be

Add the files you want to check

Choose several at once, or drop them here.

Any file: photos, signatures, PDFs, Word files. Up to 50 at a time; photos up to 50 MB and PDFs up to 100 MB are read in full. Processed on your device, never uploaded.

Checked files

    Files are read by your browser on this device and are never uploaded. Closing the page forgets them.

    What the checker reads, and what it cannot do

    Upload forms usually reject a file for one of four reasons: the wrong type, the wrong size, the wrong pixel size or page count, or a file that is damaged. The checker reads each of these from the file itself, the way a strict portal would, and shows them in plain words.

    Open Check against a form’s requirement to type what the form asks for, such as JPEG or PDF, 20 to 50 KB, 200 × 230 px or at most 2 pages. Each file then gets a table of the rules with a pass or fail for each one. A pass means the file meets the rules you typed; a portal can still have rules it does not state.

    Removing photo metadata

    Remove metadata works on JPEG and PNG files. It deletes the sections that hold EXIF data (camera, dates, GPS location, serial numbers, embedded previews), XMP, IPTC, comments and PNG text, and any extra data stored after the end of the picture, such as the video part of a motion photo. The picture data itself is copied byte for byte, so quality does not change. The colour profile is kept so colours look the same, and if the photo relies on an orientation setting to appear upright, that one setting is kept. The cleaned copy is read back and its pixels are compared with the original before you can download it.

    PDF and Office files are read-only here. Their details can be stored in several places, including older copies left by incremental saves, so removing some of them would look private without being private. Export a fresh PDF from the original document instead, or use the privacy option in the program that made it. To build a new PDF from plain text, use text to PDF.

    Turning a Word, Excel or PowerPoint file into a PDF

    ApplyReady does not convert Word, Excel or PowerPoint files. A faithful copy needs the program that laid the document out; a conversion in the browser would quietly lose tables, headers and fonts. The program you wrote it in makes the PDF in a few clicks:

    Spreadsheets and slides work the same way: Excel and PowerPoint as in Word, Google Sheets and Slides as in Google Docs, and LibreOffice Calc and Impress as in Writer.

    Then add the PDF here to check its page count, page size and file size against the form. If it is over the limit, Compress PDF makes it smaller, and Merge PDF joins it with other documents.

    Limits

    Photos up to 50 MB and PDFs up to 100 MB are read in full; larger files show only their type and size, to keep the browser responsive. Metadata in HEIC photos is detected but not read, and HEIC files cannot be cleaned here. Everything happens on this device: see your data for what ApplyReady stores, which for this page is nothing. For the reasons portals give when they refuse a file, see common upload errors and their fixes, and for DPI and centimetres, pixels, centimetres and DPI.

    Questions

    Why does a portal say my JPG is invalid when it opens on my phone?

    The file is often a different type with a .jpg name, for example a PNG or HEIC photo that was renamed. Phones and computers open it anyway because they look at the contents, but a portal that checks the contents refuses it. The checker shows the real type next to the name. To get a true JPEG, open the photo in the image resizer and download it as JPEG.

    Is a 50 KB limit the same as 50,000 bytes?

    Not always: portals count 1 KB as either 1,000 or 1,024 bytes, so a 50 KB limit is 50,000 or 51,200 bytes. The checker shows the exact size in bytes, and in KB and MB the way every ApplyReady tool does (1 KB = 1,000 bytes, rounded up). When you enter a limit, a file passes only if it is at most 50,000 bytes, which fits however the portal counts.

    What DPI is my photo, and does it matter?

    DPI is a number stored inside the file that says how large the picture should print. Many phone photos store 72 DPI or none at all. It does not change the pixels, so a portal that asks for a pixel size checks pixels, not DPI. When a form gives a size in centimetres and a DPI, multiply to get pixels, as explained in the guide on pixels, centimetres and DPI.

    Does removing metadata lower the quality of my photo?

    No. The checker removes the metadata sections and copies the picture data byte for byte, without compressing it again. It then reads the cleaned copy back and compares its pixels with the original before offering the download. The file usually gets a little smaller.

    Can it remove metadata from PDF or Word files?

    No. PDFs and Office files are only inspected here. Their details can be stored in several places inside the file, including older copies kept by incremental saves, so a partial clean would look private without being private. Use Word’s Inspect Document, LibreOffice’s option to remove personal information on saving, or export a fresh PDF from the original document.

    Is my file uploaded to check it?

    No. The checker reads the file with your browser on this device. ApplyReady has no server that receives files, and the page’s Content Security Policy stops it from sending data anywhere else.