Unsupported File Type?
An extension such as .pdf or .xlsx is only a filename label. Check what the file actually contains and compare that with the destination’s accepted types before converting or renaming anything.
If the internal signature or container does not match the extension, changing the name alone can make the problem harder to understand. ARADURU checks the actual format first for supported types.
Do not change the original file just to test a guess. Pick the closest situation and move to the matching ARADURU check.
Add the destination’s allowed extensions if you know them. The result separates extension rules from detected-format evidence.
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?
“Unsupported file type”
Compare the service’s allowed list with both the extension and the detected format.
The extension looks correct
The file may be mislabeled, damaged, or a different container than the filename suggests.
You plan to rename the file
Do not treat a rename as a conversion. Confirm the actual format first.
A practical order before you retry
Detect common formats from signatures or container structure rather than the extension alone.
Compare detected format and extension for mismatch evidence.
Check the destination’s allowed type list when you provide it or load a verified profile.
Inspect supported file structures so a damaged file is not misdiagnosed as merely unsupported.
A type error can mean three different things
The destination may truly disallow the format, the extension may not match the file, or the service may be using a broader server-side policy that ARADURU cannot see. The result should narrow those possibilities before you convert the file.