File compatibility checker for upload requirements

Use a report when you want facts before editing

This page suits a final check before submission or a controlled investigation of a rejected file. You may already have an export that looks right and want to see whether its measurable properties agree with the receiving site's rules. Running the check does not rewrite the original.

The detailed report differs from the guided upload workspace. Here you stay with one read-only inspection and interpret its findings. The guided workspace is useful when you want to move from a basic diagnosis towards applicable corrections. Choose the route that matches the next decision you need to make.

Select the saved file you will actually submit. Checking a source document before exporting it does not establish the properties of the later PDF or image. If you change the file after checking, run the report again on the new copy.

If several people are preparing the submission, record which version was checked. A report about yesterday's export should not be attached to a revised file without another inspection.

Set only the rules you have evidence for

The allowed-formats options, maximum-size field and minimum or maximum image dimensions are all optional. Populate them from the destination's current instructions. Leaving them blank keeps the corresponding compatibility condition unverified; it does not silently grant permission.

Choose the file-size unit explicitly. KB and MB use decimal counts of 1,000 and 1,000,000 bytes; KiB and MiB use 1,024 and 1,048,576 bytes. An exact-bytes option is available when the receiving page gives a precise figure. The report displays actual bytes alongside its compact size label, so a rounded number does not hide an over-limit file.

The error-text box can provide simple troubleshooting suggestions based on words in the message. It does not contact the website, understand private account policy or convert every sentence into a verified requirement. Enter the supported rules explicitly and treat suggestions as starting points.

Bring the published rules from a guide

Selected upload guides now open this same checker with their reviewed technical rules already filled in. The panel names the service, links to its published instructions and shows the review date. It also explains when a conservative byte interpretation is used or when the rule applies only to a particular service rather than the whole platform.

You can edit those settings, but the page then labels them as customised rather than presenting them as the unchanged reviewed preset. Clear pre-filled rules to start again. A link supplied by someone else cannot make its own source address or a verified=true parameter into an official endorsement.

The square-image option compares measured width with height. It does not crop a photograph, stretch a face or judge composition. Other conditions such as a minimum file size, colour profile, compression ratio, evidence content and portal acceptance remain outside the automatic checks.

What supported inspection adds

For recognised images, the detailed inspector reads available structural information such as dimensions and checks limited container framing. For PDFs, it attempts to parse the document and obtain page information. These are useful checks, but they are not a complete audit of every possible feature or a full image-quality assessment.

Supported signatures include common JPG, PNG, WebP, GIF, HEIC and PDF content, with format-specific limitations. HEIC recognition does not supply pixel dimensions before compatible decoding. A specialised or incomplete file can remain unsupported even when its filename looks ordinary.

The input limit is 25 MiB for this single-file check. PDF processing is bounded to supported documents of up to 80 pages. Resource limits protect the browser workflow; they are not statements about what the destination permits. A document outside this tool's scope may still be acceptable elsewhere.

Understand the three report outcomes

Issues found means at least one supported check reported a problem. Read each finding separately. A size failure calls for a different action from an extension mismatch, and an encrypted PDF requires a different authorised workflow from a picture with excess width.

Incomplete means the available comparison does not settle the requirements. You may have supplied no measurable rules, an extension may disagree with recognised content, or image dimensions may be unavailable. Determine which information is missing before treating the report as a reason to convert anything.

Checks passed means no issue was found under the tested rules. It does not certify document authenticity, photographic composition, accessibility or acceptance by a receiving portal. Read the limitations as part of the result, not as a separate optional warning.

A worked example of reading several findings

Suppose a fictional form permits JPG images up to a stated size and at least 600 pixels wide. You select a PNG that is 500 pixels wide. Even if its byte size is small enough, the format and minimum width disagree with the requirements. Compressing it further would not resolve either condition.

A real JPEG conversion could address the format. Increasing the width could satisfy a number while leaving insufficient detail, so a better original may be needed for the image quality. The checker cannot choose which visual compromise the recipient will accept.

For a second example, consider a readable PDF with a filename ending .jpg. Correcting that name may address the mismatch if PDF is allowed. Converting the PDF into an image would be an unnecessary and potentially disruptive response when only the label was wrong.

Treat PDF and image rules separately

Image pixel inputs do not check PDF paper geometry. A PDF may contain several pages of different sizes, and its page dimensions are expressed in points. Use the PDF page size checker for that question and review all relevant pages in a suitable viewer.

This compatibility form has no automatic rule field for a maximum PDF page count, a required paper size or a minimum byte size. You can inspect some facts, but unsupported conditions need a manual comparison. Do not assume a green status covers rules the form never asked you to enter.

Encrypted PDFs are not supported for processing. Obtain an authorised acceptable copy instead of expecting a compatibility report to remove protection. The report's ability to identify an issue is separate from the availability of a correction.

Use the next tool only for the problem you found

If the only issue is a misleading extension, consider the safe filename converter. If the actual encoding is excluded, choose a supported format conversion. If bytes exceed a limit, examine a suitable compression route while preserving readable content and required features.

Make My Files Work's PDF compressor attempts lossless repacking; large scanned pages may not shrink enough. Image outputs can change quality or transparency depending on the operation. Check each tool's explanation and inspect any downloaded result before returning to the destination.

When a file meets the entered conditions but still fails elsewhere, investigate the receiving service's session, account rules or additional checks. A support request with the measured facts and exact error is more useful than an unsupported claim that the portal must be wrong.

Questions that come up