Fix Copilot ‘File Type Not Supported’ Error When Uploading

Official documentation checked October 14, 2026.

“File Type Not Supported” needs the exact Copilot experience, account, upload method, and file. Microsoft publishes different format lists for conversation attachments, Microsoft 365 app workflows, and Notebook references. A format accepted in one workflow is not automatically accepted everywhere.

Keep the original file. Check the applicable format and size rules, then create a verified conversion copy only if necessary. Do not remove encryption or use an unapproved online converter simply to make an upload succeed.

Why Copilot May Reject a File

Microsoft’s conversation upload guide lists documents, images, and text/markup files, with up to 20 files per conversation and 50 MB per file. It explicitly supports PNG and JPEG images as well as the listed document and text formats. Check this workflow’s limits before uploading.

The separate Microsoft 365 format guide describes account and task scopes, including additional document, spreadsheet, code, and email formats. Its broad list is not a guarantee that every app’s file picker accepts every listed extension. Use the guide for your actual account and task, then the message shown by that feature.

An extension also does not prove the internal content is valid. A renamed file, a damaged export, insufficient permissions, or an unsupported attachment route may need separate investigation. The public pages checked do not document a universal UTF-8-only parser, a required BOM choice, or one internal extraction engine explaining every failure.

Steps to Fix the File Type Not Supported Error

1. Record the workflow and file details. Note whether you are attaching to Chat, referencing a file in Word, adding a Notebook reference, or asking about an Outlook attachment. Record the account/plan, extension, size, storage location, and exact message. Check the original in its normal application.
2. Check the applicable list before converting. For ordinary conversation upload, compare the extension and size with the conversation guide. For an app or Notebook reference, use its current specific guidance. RTF and image support differs by workflow, so check the applicable feature before making a conversion copy.
3. Create a conversion copy using the native application. Microsoft’s format guide suggests conversions such as .doc to .docx and .odp to .pptx when needed. Use the application’s actual Save As or Export control and a new filename. Merely changing .odt to .docx in File Explorer is not conversion. Keep macro-enabled or feature-rich originals because exporting can lose features.
4. Inspect the converted content. Reopen the copy. Compare key paragraphs, table rows, dates, numbers, formulas where relevant, and any required labels with the original. A PDF export may preserve appearance while changing editability or calculation behavior; choose the format that fits the task.
5. Attach through the supported control. The conversation guide uses +, then Add images or files. Select the copy and confirm it appears as an attachment. In Word, the current drafting guide describes typing / to choose an available reference source. Follow the options offered by that app and account.
6. Test known content. Example: “In the attached report, what value appears in the Revenue total row, and where is it stated?” Inspect the file yourself. An accepted attachment is not proof every page or number was extracted correctly.

For text or CSV with garbled characters, compare a few known values in the source editor. Export a UTF-8 copy from an approved editor or native application if appropriate, then verify accents, delimiters, quoted fields, and line breaks. This is a text-integrity check, not a verified universal Copilot encoding requirement. Do not repeatedly switch BOM settings without evidence.

If Copilot Still Shows the Error After Conversion

The file is protected or access is restricted

Check the source access with its owner. Microsoft’s Purview guidance explains that labeled encryption can be supported with appropriate VIEW and EXTRACT rights; it is not universally unreadable. Password-protected files have separate constraints, including a documented already-open, same-app data-in-use case. That does not guarantee a direct upload works. Use an authorised supported path, and keep passwords, sensitivity labels, and required DLP protection intact.

The file is too large or the conversation already has many files

For ordinary Chat upload, check the current 50 MB and 20-file rules. Start a new conversation with a checked source brief when that conversation’s file count is reached. If splitting is appropriate, make coherent local copies with an index and retain tables/notes together. Do not send confidential documents to a random online PDF splitter.

A scanned PDF produces poor extraction

Do not assume every scan must fail or every accepted scan is fully read. Check a known passage and number. If OCR is required, use an approved tool on a copy, inspect its recognized text, and verify names, columns, and decimals against the images. The supported image list does not guarantee accurate scan-to-table conversion.

A small supported sample also fails

Try a newly created non-sensitive sample using the same upload route. Record whether the problem follows one file or the account/client. If only the original fails, provide a permitted minimal reproduction through support. If all samples fail, investigate client, service, and account conditions before repeatedly changing extensions.

Conversation Uploads and App References Compared

A local filesystem path pasted into a prompt is not an uploaded file. Use the authorised upload or cloud reference supported by the experience. Do not assume every third-party cloud source or Outlook attachment must first be downloaded: available reference routes differ. Keep the original, conversion method, and verified source details with your troubleshooting record.