Choose where your file is going. See the published limits, then check your file against the rules we can measure.
15 destination profiles · source links and review dates included
ChatGPT image input
Image attached to a ChatGPT conversation · image
Check the published ChatGPT image formats, per-image size limit, and still-image requirement without claiming that the model will interpret the image correctly.
Matching format and size rules cannot prove that ChatGPT will correctly read small text, count objects, interpret a chart, or understand the image.
Upload quotas, account or plan restrictions, safety checks, storage, and temporary service failures are not properties of the selected file.
Passing these checks means the file matches the documented rules that JPEGConvert can evaluate. It does not guarantee that the destination will accept, display, send, or rank the file.
OpenAI explains that document handling can use text retrieval and that embedded-image retrieval depends on the product plan, so a searchable text layer is a safer document baseline.
JPEGConvert samples up to the first five pages. Later pages or mixed image-and-text PDFs can differ from the sample.
ChatGPT also publishes a two-million-token limit for text and document files. File bytes do not reveal the exact tokens the service will count.
Whether embedded images and charts are analyzed can depend on the ChatGPT plan and product surface; a local PDF check cannot establish that behavior.
Passing these checks means the file matches the documented rules that JPEGConvert can evaluate. It does not guarantee that the destination will accept, display, send, or rank the file.
Claude chat also applies message-level image and context limits that cannot be evaluated from one selected file.
Passing these local checks cannot prove that Claude will interpret text, objects, diagrams, or visual relationships correctly.
Passing these checks means the file matches the documented rules that JPEGConvert can evaluate. It does not guarantee that the destination will accept, display, send, or rank the file.
Claude Projects use a separate 30 MB per-file limit. This preset is specifically for a file attached directly to a chat.
A technically valid PDF can still exceed the available conversation context or fail because of account, policy, or temporary service conditions.
Passing these checks means the file matches the documented rules that JPEGConvert can evaluate. It does not guarantee that the destination will accept, display, send, or rank the file.
Etsy warns that images over 1 MB may take longer or fail on slower connections, but it does not present 1 MB as a universal listing-photo maximum.
Etsy may compress, crop, auto-rotate, and convert color profiles after upload, so a matching source file can still look different on the listing.
These checks do not evaluate Etsy content policies, listing quality, search placement, account status, or network conditions.
Passing these checks means the file matches the documented rules that JPEGConvert can evaluate. It does not guarantee that the destination will accept, display, send, or rank the file.
Google says Gemini Apps supports most file types but does not publish a complete allowlist on the cited page, so this preset does not guess whether a format is accepted.
Gemini Apps publishes a separate 2 GB video limit. Do not use this 100 MB non-video preset to judge a video file.
Rolling quotas, stored-activity limits, Workspace administrator controls, context limits, and temporary parsing failures cannot be checked from the file alone.
Passing these checks means the file matches the documented rules that JPEGConvert can evaluate. It does not guarantee that the destination will accept, display, send, or rank the file.
Keep the message's combined attachments within 25 MB
requirement · partial local check
Google states that personal Gmail accounts can send up to 25 MB in attachments. This checker can compare the selected file with that amount, but it cannot see other attachments in the draft.
JPEGConvert treats 1 MB as 1,000,000 bytes. Google publishes the limit as 25 MB without defining a byte basis on the cited page.
The published limit applies to all attachments in the message. A pass only confirms that this one selected file is no larger than the normalized 25 MB amount.
The 25 MB personal-account limit is for the combined attachments, not a promise that each individual 25 MB file will send.
Work and school account limits can be set by the Google Workspace administrator.
A size match does not check Gmail security rules, the recipient's limits, storage availability, network conditions, or delivery.
Passing these checks means the file matches the documented rules that JPEGConvert can evaluate. It does not guarantee that the destination will accept, display, send, or rank the file.
At least 500 × 500 pixels; no more than 64 megapixels
requirement · included in local check
Both width and height must reach 500 pixels for this profile. The image may be rectangular; total width multiplied by height must not exceed 64,000,000 pixels.
Google states a 16 MB ceiling without defining its byte multiplier. This profile checks a conservative 16,000,000-byte limit; a larger result is not proof of Google rejection.
Google does not define the MB byte multiplier in the reviewed sources. 16,000,000 bytes is a conservative local check, not an exact Google threshold. Results above it require an explicit unit-ambiguity note.
The published MB multiplier is unspecified. The local byte ceiling is conservative and does not establish Google’s exact boundary.
The product-data specification lists JPEG, WebP, PNG, non-animated GIF, BMP, and TIFF. The checker compares actual encoded format rather than trusting a renamed extension.
Google explicitly limits GIF to non-animated images. This automatic animation rule applies only to GIF; it does not infer an animation policy for PNG or WebP.
Choose a larger original when the image is too small
guidance · review yourself
Google advises against enlarging thumbnails. Changing the pixel count alone cannot recover product detail or establish that an image meets its visual requirements.
Images created with generative AI need metadata declaring that source. Preserve existing IPTC DigitalSourceType declarations; conversion or metadata removal can erase them. This checker does not establish AI origin or validate those declarations.
Check the published image URL and matching extension
guidance · review yourself
The live image URL must use HTTP or HTTPS, be crawlable, and use an extension matching the real image format. A local file result cannot check the live URL, robots rules, redirects, or recrawl status.
The 500 × 500 minimum begins on 31 January 2027 for all categories and marketing methods, including main and additional image links. Before then, ordinary non-apparel and apparel minimums differ; YouTube Shopping TV already requires 500 × 500.
Review the correct product and variant, overlays, borders, and image quality against Google’s full policy. These visual and account conditions are outside this local file check.
Google does not define the MB byte multiplier in the reviewed sources. 16,000,000 bytes is a conservative local check, not an exact Google threshold. Results above it require an explicit unit-ambiguity note.
Passing these checks means the file matches the documented rules that JPEGConvert can evaluate. It does not guarantee that Google will accept, display, or rank the image.
At least 250 × 250 pixels; no more than 64 megapixels
requirement · included in local check
Both width and height must reach 250 pixels for this profile. The image may be rectangular; total width multiplied by height must not exceed 64,000,000 pixels.
Google states a 16 MB ceiling without defining its byte multiplier. This profile checks a conservative 16,000,000-byte limit; a larger result is not proof of Google rejection.
Google does not define the MB byte multiplier in the reviewed sources. 16,000,000 bytes is a conservative local check, not an exact Google threshold. Results above it require an explicit unit-ambiguity note.
The published MB multiplier is unspecified. The local byte ceiling is conservative and does not establish Google’s exact boundary.
The product-data specification lists JPEG, WebP, PNG, non-animated GIF, BMP, and TIFF. The checker compares actual encoded format rather than trusting a renamed extension.
Google explicitly limits GIF to non-animated images. This automatic animation rule applies only to GIF; it does not infer an animation policy for PNG or WebP.
Choose a larger original when the image is too small
guidance · review yourself
Google advises against enlarging thumbnails. Changing the pixel count alone cannot recover product detail or establish that an image meets its visual requirements.
Images created with generative AI need metadata declaring that source. Preserve existing IPTC DigitalSourceType declarations; conversion or metadata removal can erase them. This checker does not establish AI origin or validate those declarations.
Check the published image URL and matching extension
guidance · review yourself
The live image URL must use HTTP or HTTPS, be crawlable, and use an extension matching the real image format. A local file result cannot check the live URL, robots rules, redirects, or recrawl status.
The 500 × 500 minimum begins on 31 January 2027 for all categories and marketing methods, including main and additional image links. Before then, ordinary non-apparel and apparel minimums differ; YouTube Shopping TV already requires 500 × 500.
Review the correct product and variant, overlays, borders, and image quality against Google’s full policy. These visual and account conditions are outside this local file check.
Google does not define the MB byte multiplier in the reviewed sources. 16,000,000 bytes is a conservative local check, not an exact Google threshold. Results above it require an explicit unit-ambiguity note.
Passing these checks means the file matches the documented rules that JPEGConvert can evaluate. It does not guarantee that Google will accept, display, or rank the image.
At least 100 × 100 pixels; no more than 64 megapixels
requirement · included in local check
Both width and height must reach 100 pixels for this profile. The image may be rectangular; total width multiplied by height must not exceed 64,000,000 pixels.
Google states a 16 MB ceiling without defining its byte multiplier. This profile checks a conservative 16,000,000-byte limit; a larger result is not proof of Google rejection.
Google does not define the MB byte multiplier in the reviewed sources. 16,000,000 bytes is a conservative local check, not an exact Google threshold. Results above it require an explicit unit-ambiguity note.
The published MB multiplier is unspecified. The local byte ceiling is conservative and does not establish Google’s exact boundary.
The product-data specification lists JPEG, WebP, PNG, non-animated GIF, BMP, and TIFF. The checker compares actual encoded format rather than trusting a renamed extension.
Google explicitly limits GIF to non-animated images. This automatic animation rule applies only to GIF; it does not infer an animation policy for PNG or WebP.
Choose a larger original when the image is too small
guidance · review yourself
Google advises against enlarging thumbnails. Changing the pixel count alone cannot recover product detail or establish that an image meets its visual requirements.
Images created with generative AI need metadata declaring that source. Preserve existing IPTC DigitalSourceType declarations; conversion or metadata removal can erase them. This checker does not establish AI origin or validate those declarations.
Check the published image URL and matching extension
guidance · review yourself
The live image URL must use HTTP or HTTPS, be crawlable, and use an extension matching the real image format. A local file result cannot check the live URL, robots rules, redirects, or recrawl status.
The 500 × 500 minimum begins on 31 January 2027 for all categories and marketing methods, including main and additional image links. Before then, ordinary non-apparel and apparel minimums differ; YouTube Shopping TV already requires 500 × 500.
Review the correct product and variant, overlays, borders, and image quality against Google’s full policy. These visual and account conditions are outside this local file check.
Google does not define the MB byte multiplier in the reviewed sources. 16,000,000 bytes is a conservative local check, not an exact Google threshold. Results above it require an explicit unit-ambiguity note.
Passing these checks means the file matches the documented rules that JPEGConvert can evaluate. It does not guarantee that Google will accept, display, or rank the image.
At least 500 × 500 pixels; no more than 64 megapixels
requirement · included in local check
Both width and height must reach 500 pixels for this profile. The image may be rectangular; total width multiplied by height must not exceed 64,000,000 pixels.
Google states a 16 MB ceiling without defining its byte multiplier. This profile checks a conservative 16,000,000-byte limit; a larger result is not proof of Google rejection.
Google does not define the MB byte multiplier in the reviewed sources. 16,000,000 bytes is a conservative local check, not an exact Google threshold. Results above it require an explicit unit-ambiguity note.
The published MB multiplier is unspecified. The local byte ceiling is conservative and does not establish Google’s exact boundary.
The product-data specification lists JPEG, WebP, PNG, non-animated GIF, BMP, and TIFF. The checker compares actual encoded format rather than trusting a renamed extension.
Google explicitly limits GIF to non-animated images. This automatic animation rule applies only to GIF; it does not infer an animation policy for PNG or WebP.
Choose a larger original when the image is too small
guidance · review yourself
Google advises against enlarging thumbnails. Changing the pixel count alone cannot recover product detail or establish that an image meets its visual requirements.
Images created with generative AI need metadata declaring that source. Preserve existing IPTC DigitalSourceType declarations; conversion or metadata removal can erase them. This checker does not establish AI origin or validate those declarations.
Check the published image URL and matching extension
guidance · review yourself
The live image URL must use HTTP or HTTPS, be crawlable, and use an extension matching the real image format. A local file result cannot check the live URL, robots rules, redirects, or recrawl status.
The 500 × 500 minimum begins on 31 January 2027 for all categories and marketing methods, including main and additional image links. Before then, ordinary non-apparel and apparel minimums differ; YouTube Shopping TV already requires 500 × 500.
Review the correct product and variant, overlays, borders, and image quality against Google’s full policy. These visual and account conditions are outside this local file check.
Google does not define the MB byte multiplier in the reviewed sources. 16,000,000 bytes is a conservative local check, not an exact Google threshold. Results above it require an explicit unit-ambiguity note.
Passing these checks means the file matches the documented rules that JPEGConvert can evaluate. It does not guarantee that Google will accept, display, or rank the image.
LinkedIn permits photographs and artistic representations, but says the profile photo must reflect the member's likeness and comply with its profile-photo conditions.
Technical file checks do not establish that a photo follows LinkedIn's likeness, community, copyright, or account policies.
LinkedIn can crop or reposition the image in its editor, so meeting the pixel range does not prove how the final circular profile image will look.
Passing these checks means the file matches the documented rules that JPEGConvert can evaluate. It does not guarantee that the destination will accept, display, send, or rank the file.
Audio or video file sent to the OpenAI transcription endpoint · audio, video
Check the OpenAI transcription endpoint's published request size and locally recognizable media formats without inventing bitrate or sample-rate requirements.
The endpoint reference lists FLAC, MP3, MP4, MPEG, MPGA, M4A, OGG, WAV, and WebM. JPEGConvert can automatically recognize the seven corresponding format families listed in this check; MPEG and MPGA audio are commonly detected as MP3-compatible MPEG audio.
The cited endpoint also accepts MPEG and MPGA extensions. JPEGConvert may normalize their recognizable audio contents as MP3 or leave an unusual container for manual checking.
A supported MP4 or WebM container still needs usable audio. This local check does not currently prove that an audio stream is present.
Authentication, billing, rate limits, model availability, request parameters, and network failures are API conditions rather than file properties.
Passing these checks means the file matches the documented rules that JPEGConvert can evaluate. It does not guarantee that the destination will accept, display, send, or rank the file.
USAJOBS accepts standard PDFs but says it does not accept PDF portfolio files.
Some agencies do not accept resumes through USAJOBS and may send applicants to a separate agency system with different rules.
Matching file size, type, and PDF page count does not check required resume content, accessibility, formatting quality, or job-specific instructions.
Passing these checks means the file matches the documented rules that JPEGConvert can evaluate. It does not guarantee that the destination will accept, display, send, or rank the file.
This is web compatibility guidance, not a universal website upload requirement. A CMS, CDN, host, theme, or client specification can impose different rules.
JPG does not preserve transparency and uses lossy compression. PNG preserves transparency and sharp edges but can be larger for photographs.
Passing these checks means the file matches the documented rules that JPEGConvert can evaluate. It does not guarantee that the destination will accept, display, send, or rank the file.
It means the file matches the selected rules that this tool can inspect. Account settings, visual content, upload-field differences, and later policy changes can still affect acceptance. Recommendations are labeled separately from requirements.
Use your destination’s current instructions when they differ. For another form, enter custom rules.