Social preview image upload fails silently — asset 404s, doesn't even render in Settings preview

[viorizz]

🏷️ Discussion Type

Bug

Repo: viorizz/diskutility (public, https://github.com/viorizz/diskutility)

I uploaded a custom social preview image via Settings → General → Social preview. The upload appears to "succeed" in the UI, but the resulting image never actually becomes available:

• The og:image / twitter:image meta tags on the repo page correctly reference a repository-images.githubusercontent.com URL, but fetching that URL returns HTTP 404 with body:

  {"ErrorCode":"WebContentNotFound","HttpStatusCode":404}
  

• The preview thumbnail on the Settings page itself also fails to render — so this isn't just a CDN propagation delay, the asset doesn't seem to exist on GitHub's backend at all.
• Tried this twice, with a fresh image both times (plain sRGB JPG, 1280×640px, no transparency). Both uploads produced a new asset hash, and both 404:
  • https://repository-images.githubusercontent.com/1342287089/425d5abd-cc90-4e76-af84-40177a2798fa
  • https://repository-images.githubusercontent.com/1342287089/bd4fceee-7d14-4a1b-91ee-645f1342cf4a
• Tested in both Chrome and Zen browser — same result in both, and confirmed server-side via curl independent of any browser cache.

Impact: Because the og:image is broken, social platforms (tested on Twitter/X) fall back to GitHub's generic default card instead of the custom image, since their crawlers also hit the 404.

Expected: Uploaded social preview image should be served successfully and reflected in the Settings preview and in the page's meta tags.

Actual: Asset returns 404 from repository-images.githubusercontent.com immediately after upload, consistently across two separate upload attempts.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Vendetaaaa]

Heyo,

This is a known issue caused by a server-side platform regression. It is not caused by your browser, cache, or image specs (such as format and/or dimensions).

The issue

GitHub successfully distributes an ID for og:image and/or twitter:image meta tags to your HTML, but the backend (via Azure Blob Storage) fails to persist the file; afterwards, the settings thumbnail cannot be fetched or rendered.

The workaround

Until a fix is released, you can go into Settings > General > Social preview, and clear the broken custom social preview. This will revert the metadata back to GitHub's standard fallbacks.

Proceed with caution and document this. You can also open up a direct ticket to GitHub Support about the situation.

Happy coding!