Step 1
Name the destination
Consumer apps, projects, workspaces, and APIs can publish different file rules.
AI file guide
Fix Files Rejected by ChatGPT, Claude, or Gemini
Check a file against published AI upload rules, choose the smallest useful repair, and tell a file problem from an account, quota, network, or service failure.
Quick answer
What you need to know
Start with the destination's current rules, then check the file's detected format, size, image dimensions, and PDF page or text properties that can be inspected locally. Treat rotation, tiny text, scan quality, and heavy compression as quality guidance. If a compliant test file also fails, investigate account, quota, policy, network, or service status instead of repeatedly converting the original.
- Best for
- People preparing images, PDFs, documents, or audio for ChatGPT, Claude, Gemini, or an AI transcription workflow.
- Start with
- Prepare a File for AI
- Privacy
- Processed in your browser
Compatibility repair map
What does the upload failure actually tell you?
Check the exact AI product and upload surface, inspect only the file properties that can be checked locally, and make the smallest repair supported by the evidence.
- Step 2
Check local properties
Compare detected format, byte size, dimensions, animation, and relevant PDF properties with the current published rules.
- Step 3
Make one targeted copy
Convert, resize, compress, extract pages, or use OCR only when the error or check points to that change.
The repaired copy uploads
Inspect what the AI can use
Check page completeness, text legibility, chart clarity, orientation, and audio quality; acceptance does not guarantee comprehension.
A small supported test also fails
Check non-file causes
Review account access, quota, workspace policy, browser session, network, and service status.
Do this first
Repair an AI Upload Without Guessing
Use the same order for an image, PDF, document, or audio file so each change answers a specific question.
- 1
Choose the exact AI destination
Select the product and upload surface you are actually using because ChatGPT, Claude, Gemini, and their APIs do not share one universal rule set.
- 2
Inspect locally checkable rules
Compare detected format, byte size, image dimensions, animation, and relevant PDF properties with the destination's current published rules.
- 3
Apply one targeted repair
Convert, resize, compress, extract pages, or improve searchable text only when the check or exact error points to that change.
- 4
Retry and separate service failures
Upload the repaired copy once; if a small supported test file also fails, check quota, account access, policy, session, network, and service status.
01
Know What a Local Compatibility Check Can Prove
A browser can inspect concrete file properties, but it cannot promise that an external AI service will accept, index, understand, or answer accurately from the file.
- Locally checkable properties include detectable format, byte size, image dimensions, animation state, and selected PDF page or text properties.
- Published rules differ by product surface: ChatGPT image and general file uploads, Claude chats, projects and vision inputs, Gemini Apps, and API endpoints have separate limits.
- Passing means the file meets the rules that were checked; it is not an acceptance, comprehension, or answer-quality guarantee.
02
Match the Repair to the Destination and Error
The safest repair preserves the source and changes only the property that conflicts with a current rule or a specific upload message.
- ChatGPT's image guidance lists PNG, JPEG, and non-animated GIF with a 20 MB per-image limit, while general file uploads publish a separate 512 MB hard limit and document rules.
- Claude's upload and vision documentation separates chat, project, PDF, and image constraints; use the rule for the surface you are using rather than mixing those limits.
- Gemini Apps publishes file-count, file-size, duration, and account-dependent rules, while OpenAI transcription API inputs have their own supported media formats and endpoint limits.
- Keep the original. Create a repair copy, then compare transparency, animation, page completeness, searchable text, readability, and audio playback as applicable.
Go deeper
Fix a PDF That Will Not Upload
Find the likely cause of a failed PDF upload, including file size, password protection, damage, filename issues, or unsupported document features.
03
Check Quality and Non-File Causes Before Repeating the Upload
Some problems cannot be reduced to a green or red file rule, so finish with a visual or listening check and one controlled retry.
- Treat rotation, tiny text, dense charts, scan contrast, aggressive compression, and noisy audio as quality guidance that needs human review.
- If the original and a small supported test file both fail, investigate account entitlements, quotas, workspace policy, browser session, network, and service availability.
- Recheck official documentation when a platform changes behavior; AI upload limits and supported surfaces can change independently.
Quick questions
AI File Compatibility FAQ
Why does ChatGPT reject an image that opens on my computer?
The local app may support a format or file size that the ChatGPT upload surface does not. Check the detected format and byte size first, then orientation, animation, dimensions, and the exact upload error.
Does passing the checker mean Claude or Gemini will accept my file?
No. A local check can show that selected published file rules are met, but it cannot see account limits, workspace policy, outages, or every server-side validation rule.
Should I convert every AI image upload to JPG?
No. Convert only when the destination rejects the source format and a still JPG copy is appropriate. JPG removes transparency and animation and can introduce compression artifacts.
Why can an AI upload a PDF but miss text or charts inside it?
Upload acceptance is different from content extraction. Scanned pages, tiny text, rotation, complex layouts, and product-specific PDF handling can reduce usable results even when the file passes basic checks.
How do I know whether the file or the AI service is failing?
Retry with a small supported test file in the same account and session. If that also fails, account access, quota, policy, network, session, or service availability is more likely than the original file.
Can I use the same limits for an AI website and its API?
Do not assume so. Consumer apps, projects, enterprise workspaces, and API endpoints can publish different supported formats, size limits, page limits, and duration rules.
Remember this
The short version
- Check destination-specific rules before converting the file.
- Separate hard, locally inspectable properties from quality guidance and non-file failures.
- A passed local check narrows the problem; only the destination can confirm upload acceptance and usable results.
- Preserve the source and make the smallest repair that the evidence supports.
Ready to work
Open the tool you need
Pick the step that matches your file. Each tool runs in your browser.
Prepare a File for AI Choose an AI destination, inspect the locally checkable rules, and open a relevant repair path without uploading the file to JPEGConvert. Open tool Check My File Check a file against custom format, size, dimension, page, and PDF requirements when the exact destination is not listed. Open tool Convert to JPG Create a broadly compatible still-image copy when the destination rejects a supported source format such as HEIC, WebP, or AVIF. Open tool