File Too Large to Upload?
A “too large” message only makes sense against the destination’s actual limit. Enter the exact limit shown by the service, then check the selected file before deciding whether to compress, split, or convert it.
Different destinations, account types, message types, and plans can use different limits. ARADURU intentionally leaves unknown limits blank rather than pretending one number applies everywhere.
Do not change the original file just to test a guess. Pick the closest situation and move to the matching ARADURU check.
Enter the maximum shown by the destination. ARADURU uses binary MB consistently in the checker and shows the rule used in the result.
Use the file that actually failed
Start with the same file so the result reflects the real failure, not a substitute file.
What happened when you tried to upload?
The service says “file too large”
Use the exact limit shown there and compare it with the actual file bytes.
The file looks small but still fails
The error may refer to another limit, aggregate message size, account context, or a different server-side rule.
You are considering compression
First confirm that size is really the blocker so you do not reduce quality or change formats unnecessarily.
A practical order before you retry
Measure the selected file size and compare it with the rule you provide.
Keep the observed bytes and limit bytes separate in the rule evaluation.
Check file type, filename, and supported structure at the same time so size is not blamed for a different problem.
When a verified destination profile is available, switch to it instead of manually copying rules.
Only change the file after the size rule is confirmed
If size is the actual blocker, the best next step depends on the file: compressing media, reducing embedded assets, splitting a document, or using a supported transfer method may help. ARADURU should first establish the rule that failed.