If a Gmail attachment’s name looks garbled, compare where the name first changes. The message’s displayed filename, the downloaded filename, and the text inside the document are different things. Renaming a local file may make its name readable without repairing its contents or explaining the original cause.
Compare the original and the received copy
Ask the sender to confirm the exact filename and actual file type through an established channel. Check whether the problem appears in Gmail’s attachment tile, only after downloading, or only inside the application used to open it.
Keep the original received file unchanged while investigating. If the document itself contains unreadable text, changing the attachment’s name will not fix that content problem. The sender may need to create a compatible export from the source application.
Use a small, controlled comparison
For a trusted file, the sender can attach a separate test copy with a short, descriptive filename while preserving the correct extension. Compare the received name in another supported browser or device if available. This can narrow the issue to a sending path, receiving interface, or local filesystem behavior.
Do not conclude that Gmail forbids a language’s characters merely because one test fails. Naming and encoding can be affected elsewhere in the workflow. These comparisons are diagnostics, not a guaranteed Gmail-specific recoding fix.
Preserve file type and security checks
If you rename a verified local copy for convenience, keep its real extension and inspect the application’s open result. Do not change an executable-looking extension to a document extension to make the file seem familiar.
Garbled characters do not establish whether a file is safe. Check unexpected attachments and sender requests independently, and leave security protection enabled. Avoid uploading confidential files to an unknown online filename-repair service.
If the discrepancy persists, report the original and resulting names, actual format, sending application, browser or device, and non-sensitive error details. Use a harmless reproduction rather than a private attachment. Google’s download guidance helps verify the saved destination and file association; it does not provide a universal filename-encoding repair for every sender and operating system.
Browse Gmail & Google Account help
References
Reviewed against the linked official and developer guidance on October 27, 2026. Available options and screen labels can vary by account, device, region, and organization policy.