THE SHORT ANSWER

Copy the organizer’s exact requirements into a checklist, inspect the final exported files, and confirm acceptance in the submission system. A local file checker cannot approve an entry or verify every rule.

Turn the rules into separate checks

Photo submission instructions often mix several different requirements in one paragraph. Break them into format, pixel dimensions, file size, filename, quantity, and deadline. Add any rules about aspect ratio, editing, ownership, or subject matter as separate manual checks. Keep a link or saved copy of the organizer's instructions and note when you checked them, because an event can revise its requirements.

Do not assume that a file accepted by last year's form will work this year. Likewise, a social media image that looks sharp on a phone may be too small for an exhibition entry. The goal is not to make the largest possible file; it is to produce the specific file the recipient requests while keeping your original photograph untouched.

Understand what each number describes

Pixel dimensions describe the image grid: 2400 by 1600 pixels, for example. File size describes how much storage the encoded file uses. Those are related but not interchangeable. Two images with the same pixel dimensions can have different file sizes because their content and encoding differ. Changing a filename from .png to .jpg does not convert the image format.

Aspect ratio describes the relationship between width and height. A 2400 by 1600 image has a 3:2 ratio. If a form asks for a square, simply reducing both dimensions by the same proportion will not make it square; you need a square crop or another explicitly permitted treatment. Keep important content away from the crop boundary and inspect the exported result.

If instructions say only 2 MB without defining the unit, avoid aiming exactly at the boundary. Some tools use decimal megabytes and others use 1,048,576 bytes per displayed MB. Entry Check uses the latter calculation. Leave a sensible margin below the stated limit and use the organizer's upload result as the final technical check. Do not interpret a local green result as a promise of acceptance.

Work on copies in a clean submission folder

Create a folder containing only the files you intend to submit. Export from your original into that folder, using clear filenames that follow the organizer's pattern. If the rule is surname-number.jpg, do not add a descriptive suffix unless it is allowed. Preserve a separate copy with a human-friendly name if that helps your own archive.

For a concrete example, imagine an event asks for JPEG files, at least 1800 pixels on the short side, no more than 4000 pixels on the long side, and filenames starting with entry-. A 3000 by 2000 JPEG named entry-01.jpg passes those dimension and prefix checks. It could still fail a file-size limit, an aspect-ratio rule, or a restriction on image editing. Each requirement needs its own decision.

Open every exported file at a useful viewing size. Check for an unexpected crop, wrong orientation, a blank image, or a watermark left from an earlier export. Technical properties alone cannot tell you whether the intended image is present. If there are multiple entries, compare the folder contents with your numbered list rather than relying on how many thumbnails you remember seeing.

Use automated checks for the repetitive parts

Entry Check examines supported JPEG and PNG files against the values you enter for dimensions, file size, format, and filename pattern. You supply the rules; it does not fetch an event's policy or interpret legal terms. Use its results to identify files that deserve another look, then review the written instructions again before submitting.

Filename patterns use simple wildcards. An asterisk can stand for a variable part of the name; it is not a full regular-expression system. Keep the rule as narrow as the event requires, and manually compare a sample filename with the instructions. A broad pattern may accept names the organizer would reject. Unsupported or unreadable files need a separate export or investigation.

Finish with the recipient's confirmation

Upload early enough to fix a problem without rushing. Wait for the form to finish, inspect any preview it provides, and confirm the number of files received. A selected file in your browser is not the same as a completed submission. If the process provides a receipt or confirmation number, save it with the final files and the rules you followed.

Do not repeatedly resubmit just because a confirmation email is slow. First check the page's status and the organizer's stated procedure. Keep a short note recording what you submitted and when. This makes a later correction or support request easier to explain and helps you avoid accidentally sending an earlier draft from your downloads folder.

KEEP THIS HANDY

Your quick checklist

  • Save the current submission rules.
  • Check format, dimensions, size, and name separately.
  • Open the final exported files.
  • Review rights and content rules manually.
  • Keep the completed submission receipt.

Prepared with AI assistance and checked against the scope of our tools. Examples are illustrative; they are not claims of hands-on testing. How we make these guides.