Expanded file type support for issue attachments [GA]

[tuves]

Hello Community! 👋

uploading.mp4

You can now upload a wider range of file types to issues, pull requests, discussions, and comments, making it easier to share code, data, logs, and more.

New supported file types include:

• Code and data (.py, .yaml, .yml, .css, .xml, .html, .htm, .js, .sql, .java, .c, .cpp, .sh, .php, .ts, .tsx, .cs, .ipynb, .pdb, .xlsm, .tsv, .drawio, .bin)
  Documents (.rtf, .doc)
• Text and email (.debug, .msg, .eml, .copilotmd)
• Images (.bmp, .tif, .tiff)
• Audio (.mp3, .wav)

For more details, see the GitHub documentation.

Let us know your thoughts below on these new updates!

[Atulin]

BMP and TIFF, but not Webp and AVIF?

[jonnyawsom3]

Right now we have users renaming JXL files to JPG just to upload them to Github. It still loads and renders correctly, but it's an annoying workaround just because it excludes the extension.

[Salman-Sali]

what exactly goes on to support something the browser can already render?

[QuickWrite]

what exactly goes on to support something the browser can already render?

I would assume that it is mostly a security thing. Yes, the browser can already render these files, but as they are getting uploaded to a server they have to be checked so that they are also that what they claim to be.

Otherwise it would be easy to upload malicious files (to harm the servers and to also potentially harm the client that gets the content served).

[Norbiros]

@Atulin support for .webp is already in the works and coming soon.

@labudis I didn’t see an open discussion for this - will it also make .webp files render as images in the Files Changed tab instead of appearing as unknown binary files?

[tats-u]

AVIF request: https://github.com/orgs/community/discussions/138164

[0fbcb238c0]

What about support for JPEG XL?

[labudis]

Thank you for the suggestion, we will note this down for potential future additions!

[tats-u]

Keep it ready to be activated whenever Chrome/Edge/Chromium re-implements it and Chrome/Edge/Chromium and Firefox activate it in stable builds.

[anonymous234]

It might take another 5 years, but JXL is the inevitable winner despite Google's boycott and Mozilla's hesitancy. It's just so much better than any other format by every metric. Perfect opportunity to stay ahead of the curve.

[justlevine]

Are there matching permissions to lock this down or will us FOSS maintainers now need to sift through attachments on top of the regular MCP spam?

[goodusername123]

I apologize if you received a notification or email, I mistakenly posted my general comment as a reply to yours and then deleted it

[goodusername123]

Hello! I find the list of supported/allowed files types to be quite lacking even after having these new ones added. below is a list of my suggestions which includes many formats that are commonly exchanged alongside a few formats that are more "niche" but still completely valid and recognized:

• Audio (.ogg, .flac, .m4a, .aac, .wv, .weba, opus, .wma, .oga)
• Compressed/Archive (.rar, .7z, .zst, .lz, .bz2, .xz, .cab, .br)
• Images (.webp, .jxl)

Additionally I would like to state that I have encountered many situations over time in which I am frustrated being unable to upload these types of files and have resorted to faking the file extension just so GitHub will let me upload along with occasionally seeing other users with similar frustrations.

[labudis]

Thank you so much for your detailed feedback and suggestions regarding supported file types. We really appreciate you sharing which formats are most important to you and describing your real-world experience.

A few key points to share about how we approach adding new file extensions:

• We use data to inform which new file extensions to support. We regularly track which file types are failing to upload and prioritize those with the most demand from users.
• Some file extensions have potential security impacts, so we perform a thorough security review before approving new extensions. This means that, in some cases, certain formats may not be allowed even if there is user demand.
• WebP support is already in the works and will be available soon.
• We will consider the other extensions you suggested as we continue to prioritize and expand our list of supported formats.

Thank you again for sharing your feedback and helping us improve the experience for everyone!

[Atulin]

Yes, that is the top post. We have all seen it, no need to quote it

[porg]

In 2021-09 the GitHub community requested: Native WebP image support

Now 2025-08 according to @labudis

WebP support is already in the works and will be available soon.

Glad that GitHub will finally get it!

[porg]

Official now:
https://github.blog/changelog/2025-08-28-added-support-for-webp-images/

[GJCRESYM]

Hello,
We are using Quarto in our project to render GitHub Pages. While working with GitHub Issues, we noticed that attaching .qmd files is not supported.
Would it be possible to add support for .qmd files as an allowed attachment type in issues? This feature would be especially helpful for projects that rely on Quarto documents.

[cyqsimon]

Zstandard compression performs significantly better than gzip in both speed and ratio. I implore you to consider raising the priority on this.