Bulk compatibility checker for a group of upload files

Group files by their actual requirements

Start with the receiving service's attachment checklist. A portrait photograph, a CV and a set of supporting scans may belong to one application but follow different technical rules. Keep them in separate checking groups when their accepted formats, size caps or dimensions differ.

Files in this batch share the same entered requirements. If one document is permitted as PDF and another must be JPG, ticking both formats would allow either format for every item. That would lose the distinction the application requires. A single shared check is useful only when the rules genuinely align.

Keep a simple record of which attachment belongs in which destination field. The checker uses filenames to identify results; it does not know that one file is a passport image and another is a statement. Content and document-category matching remain your responsibility.

Select a manageable batch

The current limits are 12 files, 25 MiB per file and 50 MiB combined input. These are this tool's working limits, not the receiving site's upload allowance. A collection that satisfies the local cap can still violate the destination's much smaller per-file or total rule.

Choose saved files from a known folder. Remove obsolete versions before making the selection if they could be confused with final copies. Two similarly named documents can both appear in a picker, so check the selected list before running a report.

If the group is too large, divide it into smaller groups without changing the destination's rules. Keep track of which files were checked in each run. Splitting the inspection into batches does not mean the final submission can exceed a combined attachment limit.

Enter the shared rule set

Select only the formats permitted for every item in the group. Enter the maximum file size if known. The field currently uses 1,048,576 bytes per displayed MB unit, so take care with a destination using decimal megabytes or an exact byte cap.

Enter minimum and maximum image dimensions only when those conditions apply to the images being checked. Pixel rules do not describe PDF page geometry. A mixed PDF-and-image group with image dimensions entered can produce unverified dimension findings for the PDFs rather than a meaningful page-size assessment.

Do not use a guessed value to make the group appear complete. Empty requirement fields remain outside the comparison. If the service gives a minimum file size, maximum page count or a special content rule, keep those in your manual checklist because this interface does not automatically test them.

Read every file's outcome

The report separates files so you can identify which items need attention. A successful check for the first photograph does not establish that the remaining attachments are suitable. Read each filename and finding, especially when one file has a similar name to another.

A file can fail because it exceeds the stated size, uses an excluded format or cannot be sufficiently validated. A warning about a misleading extension is different from an actual byte-limit failure. Choose the next action according to that individual result.

An incomplete outcome means the report lacks a necessary basis for comparison, such as usable dimensions or supplied rules. It is not evidence that the file has been accepted. Resolve missing information where possible and preserve uncertainty where the tool cannot measure it.

Use batch results to organise the remaining work

Separate the files into those ready for your final manual review, those needing a supported correction and those needing clarification from the issuer or recipient. This is a practical working method; the tool does not create these folders or change the files for you.

For a wrong format, use an appropriate conversion on that particular source. For excess size, try a suitable reduction while retaining required information. For a misleading extension, a name correction may suffice. Do not compress every file simply because one attachment is too large.

Protected PDFs require an authorised acceptable version. An incomplete download needs a fresh source. A photo with insufficient detail may need replacing rather than enlarging. A batch report is most useful when it prevents you from applying one inappropriate fix to a varied set.

Recheck corrected copies without losing the originals

Save outputs with distinguishable names and keep the originals until submission is complete. If several downloads receive numerical suffixes, check which one is the intended final version. A folder full of similarly named attempts increases the risk of selecting the wrong attachment.

Run the relevant check again on each corrected output or on a new consistent batch. A conversion can change byte size; a resize can change dimensions; merging PDFs changes page count. The earlier report described the source, not the new result.

Review visible contents too. Open document pages and check dates, names, references and signatures. Inspect image framing and clarity. The batch checker does not assess whether the documents belong to the correct person or whether a required page is missing.

Per-file limits are not a combined submission allowance

The maximum-size field is compared with each selected file. It does not represent a total destination budget for the whole batch. Add the final attachment sizes separately where the receiving form publishes a combined cap.

A website may also limit the number of attachments or the complete request size. Those policies are outside this report's configurable comparisons. Twelve locally inspected files are not automatically twelve permitted uploads, and a ZIP archive is not an acceptable substitute unless the destination says so.

Use the receiving service's own attachment list before final submission. Confirm that every intended file is present once, that old versions have been removed and that each is in the correct field. Keep the final receipt or confirmation after the service accepts the submission.

Questions that come up