# Can't post images at all anymore?

**URL:** <https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160>\
**Category:** Site Feedback\
**Created:** [November 17, 2026, 4:20pm UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160 "2026-11-17T16:20:55Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Atamasama](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/atamasama/32/12961_2.png) [@Atamasama](https://boards.straightdope.com/u/Atamasama)\
**Post date:** [November 17, 2026, 4:20pm UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/1 "2026-11-17T16:20:55Z")

</div>

This is a new issue to my knowledge. It was pointed out in this post that a photo of Kim Jong Un couldn’t be embedded, and they had to post a link you needed to click to see it.

> [@Unconfirmed reports that Kim Jong-Un may be dead](https://boards.straightdope.com/t/unconfirmed-reports-that-kim-jong-un-may-be-dead/1033984/65):
>
> [Picture](https://images.handelsblatt.com/nUlYXN1bghJw/cover/2400/1600/18/0/0/0/0.536/0.493/topshot-this-picture-taken-between-november-15-and-16-2026-and-released-by-north-koreaaposs-off.avif) from today’s press, linked because Discourse is like it is. Would have liked to embed it, but no luck. The details here and there are very nice.

I thought that it might be an issue with the format of the image (it’s a .avif file) or because it was a large photo and it was posted after the preview pane pre-loaded it, which is the same problem we have trying to post an inline video. But I’ve tried all sorts of photos, and made sure to disable the preview pane, and I still get an error.

The specific error is:

> An error occurred: Sorry, you can’t include images, videos, or audio in posts. You can link to them within a sentence instead.

I haven’t seen this happen before today. Did something happen with the site?

---

<div class="post-metadata">

**Author:** ![Joey\_P](https://avatars.discourse-cdn.com/v4/letter/j/919ad9/32.png) [@Joey\_P](https://boards.straightdope.com/u/Joey_P)\
**Post date:** [November 17, 2026, 4:43pm UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/2 "2026-11-17T16:43:28Z")

</div>

Strange, I can’t either. I thought it was the picture since I also couldn’t upload that image to imgur, but when I tried posting a random picture from imgur, I got the same error.  
Seems like someone turned off the ability to post inline images.

ETA, threads with pictures still have pictures, so that’s good.  
ETA2, I also couldn’t post a picture to a thread that already has pictures.

---

<div class="post-metadata">

**Author:** ![Telemark](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/telemark/32/372_2.png) [@Telemark](https://boards.straightdope.com/u/Telemark)\
**Post date:** [November 17, 2026, 4:56pm UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/3 "2026-11-17T16:56:50Z")

</div>

Same here, I used the exact same method to post an image that was previously posted in a different thread and got the message. The preview shows the image, so it’s not a direct technical problem, it appears to be being prevented.

---

<div class="post-metadata">

**Author:** ![Darren\_Garrison](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/darren_garrison/32/92_2.png) [@Darren\_Garrison](https://boards.straightdope.com/u/Darren_Garrison)\
**Post date:** [November 17, 2026, 5:18pm UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/4 "2026-11-17T17:18:53Z")

</div>

Yep, just tested it, same problem.

---

<div class="post-metadata">

**Author:** ![PastTense](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/pasttense/32/14550_2.png) [@PastTense](https://boards.straightdope.com/u/PastTense)\
**Post date:** [November 17, 2026, 5:33pm UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/5 "2026-11-17T17:33:29Z")

</div>

Apparently Discourse just made a security fix:

> **[Users not in Embedded media post allowed groups can bypass upload restriction...](https://meta.discourse.org/t/users-not-in-embedded-media-post-allowed-groups-can-bypass-upload-restriction-by-copying-the-uploaded-image-link/387368/2?tl=en-4)**
>
> I don’t know if this is a new issue, but we just noticed it too: It seems like the image upload to the S3 bucket (cdck-file-uploads-global.s3.dualstack.us-west-2.amazonaws.com) happens as soon as the image is pasted. The embed check doesn’t...

and the fix:

> <https://github.com/discourse/discourse/pull/45823>
>
> Users outside \`embedded\_media\_post\_allowed\_groups\` could still embed media:
> 
> \- t…he composer accepted image, video and audio uploads, so their URLs could be reused in a post
> \- media URLs on their own line (external images, uploaded videos and audio) render as oneboxes, which \`PostAnalyzer#embedded\_media\_count\` ignored because it counted from the stripped cooked HTML
> \- video uploads render as \`.video-placeholder-container\`, not \`\<video\>\`, so they weren't counted either
> \- a link whose URL doesn't look like media but whose response is (an image served without an extension) became a media onebox after validation
> 
> This change:
> 
> \- counts rendered media (excluding rich onebox previews) and pending media oneboxes in \`embedded\_media\_count\`
> \- adds \`Guardian#can\_embed\_media?\`, used by the post validator and exposed as \`can\_embed\_media\` on the current user
> \- refuses image, video and audio uploads in the composer when the user can't embed media
> \- keeps a onebox as a link when it resolves to media its URL didn't reveal and one of the post's writers (author or editors) can't embed media, needs media review, or is a new user at their limit; the same check applies when cooking inserts a cached onebox and when post processing resolves one
> \- rewords the embedded media errors to say what is still allowed (links)
> 
> Not breaking at default settings. Sites that restrict these settings will notice:
> 
> \- restricted users can't upload audio or video in the composer, even as attachments
> \- video uploads and media URLs now count towards \`newuser\_max\_embedded\_media\` and \`skip\_review\_media\_groups\`
> \- restricted users can't save edits to older posts that contain such media
> \- for restricted users, links that only turn out to be media once fetched stay links
> 
> Ref - https://meta.discourse.org/t/387368

Chatgpt says:

> My assessment is that Straight Dope probably already had a restriction on embedded media for some user groups, but an earlier Discourse bug allowed users to get around it. The November fix began enforcing the restriction properly.
> 
> **So this is not simply a Straight Dope administrator suddenly deciding to prohibit images.** It may be an unintended consequence of a Discourse software update exposing an existing permission setting.
> 
> The question for Straight Dope administrators is whether they intended that restriction to apply to ordinary registered members.
> 
> I would be quite confident that we’ve identified the underlying cause, although we cannot yet establish the forum administrators’ intentions.

---

<div class="post-metadata">

**Author:** ![Chefguy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/chefguy/32/138_2.png) [@Chefguy](https://boards.straightdope.com/u/Chefguy)\
**Post date:** [November 17, 2026, 5:44pm UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/6 "2026-11-17T17:44:12Z")

</div>

Tried to post one from imgur with no luck. Doesn’t bode well for the monthly photo contest.

---

<div class="post-metadata">

**Author:** ![Atamasama](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/atamasama/32/12961_2.png) [@Atamasama](https://boards.straightdope.com/u/Atamasama)\
**Post date:** [November 17, 2026, 6:04pm UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/7 "2026-11-17T18:04:26Z")

</div>

Ugh… So what we’re saying, then, is that we’ve been taking advantage of an exploit in order to post images, and they’ve “fixed the glitch” (to quote _Office Space_), so now things are working the way they were always intended to.

Well that stinks. I get it, I guess, but it’s disappointing. I guess it was nice while it lasted!

---

<div class="post-metadata">

**Author:** ![RitterSport](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/rittersport/32/6326_2.png) [@RitterSport](https://boards.straightdope.com/u/RitterSport)\
**Post date:** [November 17, 2026, 6:06pm UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/8 "2026-11-17T18:06:42Z")

</div>

I think I don’t understand why that feature was not allowed – I don’t think Discourse is hosting anything, right? It’s being hosted elsewhere, and just shown here. No skin off Discourse’s nose.

---

<div class="post-metadata">

**Author:** ![Dewey\_Finn](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/dewey_finn/32/4222_2.png) [@Dewey\_Finn](https://boards.straightdope.com/u/Dewey_Finn)\
**Post date:** [November 17, 2026, 6:38pm UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/9 "2026-11-17T18:38:52Z")

</div>

I just tried with an image from Wikimedia, but no luck. It appeared in the preview window but I received the same error as in the first post of this thread when hitting reply.

Too bad, as that was a useful option.

---

<div class="post-metadata">

**Author:** ![Dung\_Beetle](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/dung_beetle/32/7945_2.png) [@Dung\_Beetle](https://boards.straightdope.com/u/Dung_Beetle)\
**Post date:** [November 17, 2026, 6:43pm UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/10 "2026-11-17T18:43:34Z")

</div>

> [@Atamasama](#):
>
> Well that stinks. I get it, I guess, but it’s disappointing. I guess it was nice while it lasted!

I hope it’s not permanent. I will be heartbroken.

---

<div class="post-metadata">

**Author:** ![Atamasama](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/atamasama/32/12961_2.png) [@Atamasama](https://boards.straightdope.com/u/Atamasama)\
**Post date:** [November 17, 2026, 6:53pm UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/11 "2026-11-17T18:53:22Z")

</div>

> [@Dung\_Beetle](#):
>
> I hope it’s not permanent.

Here is what the thread over at Discourse on the security patch info says:

> - the composer accepted image, video and audio uploads, so their URLs could be reused in a post
> - media URLs on their own line (external images, uploaded videos and audio) render as oneboxes, which `PostAnalyzer#embedded_media_count` ignored because it counted from the stripped cooked HTML
> - video uploads render as `.video-placeholder-container`, not `<video>`, so they weren’t counted either
> - a link whose URL doesn’t look like media but whose response is (an image served without an extension) became a media onebox after validation

And all of that sounds like what we’ve been doing to get YouTube videos and photos to work in posts. But now…

> This change:
> 
> - counts rendered media (excluding rich onebox previews) and pending media oneboxes in `embedded_media_count`
> - adds `Guardian#can_embed_media?`, used by the post validator and exposed as `can_embed_media` on the current user
> - refuses image, video and audio uploads in the composer when the user can’t embed media

And to us:

> - video uploads and media URLs now count towards `newuser_max_embedded_media` and `skip_review_media_groups`

What we’ve been using seem to be what Discourse calls “media URLs”, and it is explicitly blocking them. We can link to images and videos off the site, but we can no longer have it embedded in a post anymore, despite the fact that it’s being hosted elsewhere and we aren’t uploading anything.

---

<div class="post-metadata">

**Author:** ![Pardel-Lux](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/pardel-lux/32/20182_2.png) [@Pardel-Lux](https://boards.straightdope.com/u/Pardel-Lux)\
**Post date:** [November 17, 2026, 7:02pm UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/12 "2026-11-17T19:02:09Z")

</div>

Damned. And all that because I wanted to upload a picture of Kim Jong Un that seemed ridiculously weird to me.  
I’ll never do it again, I promise. They won’t let me anyway.

---

<div class="post-metadata">

**Author:** ![LSLGuy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/lslguy/32/5813_2.png) [@LSLGuy](https://boards.straightdope.com/u/LSLGuy)\
**Post date:** [November 17, 2026, 11:54pm UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/13 "2026-11-17T23:54:23Z")

</div>

> [@RitterSport](#):
>
> I think I don’t understand why that feature was not allowed – I don’t think Discourse is hosting anything, right? It’s being hosted elsewhere, and just shown here. No skin off Discourse’s nose.

When you hotlink to some image at, say, ImgBB or some random news site, you’re right that that image remains hosted at that site, whatever it is. Not at Discourse. But …

Discourse creates a thumbnail, or for vids a first frame still preview, and stores that thumbnail within their own cloud storage. Which storage Discourse (and their customers like SDMB) are paying for.

That’s the thing Discourse originally did not want everybody under the sun to be able to do: store thumbnails / previews on Discourse’s cloud servers. But their bug allowed everyone, including you and me, to do it. So we did.

And now they’ve fixed the bug and we’re prohibited again as they’d wanted all along.

It looks like _if_ SDMB wanted to pay for additional storage for thumbnails for our pix & vid cites’ thumbnails, then SDMB management could enable thumbnail caching and hence image inlining for all registered users.

---

<div class="post-metadata">

**Author:** ![Chronos](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/chronos/32/134_2.png) [@Chronos](https://boards.straightdope.com/u/Chronos)\
**Post date:** [November 18, 2026, 12:18am UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/14 "2026-11-18T00:18:05Z")

</div>

“User groups” are something created by the administrator of the site here, though, right? It sounds to me like an administrator could fix this just by enabling the “Embed Media” option for the regular user group, here. Or promote everyone to a different user group that has that option. And that that might also fix the problem that we’ve had forever with embedding YouTube videos that Discourse has never been able to help us with.

If storing thumbnails is really a problem for Discourse, then they could just… not do that.

---

<div class="post-metadata">

**Author:** ![Mean\_Mr.Mustard](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/mean_mr.mustard/32/3865_2.png) [@Mean\_Mr.Mustard](https://boards.straightdope.com/u/Mean_Mr.Mustard)\
**Post date:** [November 18, 2026, 12:30am UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/15 "2026-11-18T00:30:17Z")

</div>

I blame Biden.

mmm

---

<div class="post-metadata">

**Author:** ![TroutMan](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/troutman/32/6721_2.png) [@TroutMan](https://boards.straightdope.com/u/TroutMan)\
**Post date:** [November 18, 2026, 12:36am UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/16 "2026-11-18T00:36:48Z")

</div>

> [@LSLGuy](#):
>
> Discourse creates a thumbnail, or for vids a first frame still preview, and stores that thumbnail within their own cloud storage. Which storage Discourse (and their customers like SDMB) are paying for.

Are you sure about this? I couldn’t find confirmation that it’s actually creating and saving thumbnails on Discourse servers. Maybe it is, but that’s not how I’d expect it to work.

> [@Chronos](#):
>
> It sounds to me like an administrator could fix this just by enabling the “Embed Media” option for the regular user group, here.

If the admins still want to block upload of content but allow oneboxes to show linked content, I believe they can add us to the `embedded_media_post_allowed_groups` and set the maximum size to 0 KB ( `max_image_size_kb` and `max_attachment_size_kb = 0`). That would block all uploads but allow link rendering.

---

<div class="post-metadata">

**Author:** ![LSLGuy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/lslguy/32/5813_2.png) [@LSLGuy](https://boards.straightdope.com/u/LSLGuy)\
**Post date:** [November 18, 2026, 12:48am UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/17 "2026-11-18T00:48:29Z")

</div>

> [@TroutMan](#):
>
> Are you sure about this?

I was gathering that from my limited understanding of @PastTense’s cites in post #5. I may have screwed that up.

Ref those cites, for sure _something_ was being stored in an S3 bucket that Discourse was controlling and paying for. And that was the problem; they didn’t actually want that to happen. And now it doesn’t.

---

<div class="post-metadata">

**Author:** ![Atamasama](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/atamasama/32/12961_2.png) [@Atamasama](https://boards.straightdope.com/u/Atamasama)\
**Post date:** [November 18, 2026, 12:48am UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/18 "2026-11-18T00:48:36Z")

</div>

> [@TroutMan](#):
>
> Are you sure about this? I couldn’t find confirmation that it’s actually creating and saving thumbnails on Discourse servers. Maybe it is, but that’s not how I’d expect it to work.

This thread suggests they are.

> **[Where are Images and uploads stored?](https://meta.discourse.org/t/where-are-images-and-uploads-stored/317601?tl=en)**
>
> Please where are images and videos stored in Discourse? Our users would be uploading pictures and videos. For now, I would like to use DropBox. How do I configure this? Also, is Vimeo supported? Finally, between Vimeo, DropBox and Amazon S3,...

> By default, linked images are downloaded to local storage so that they continue to exist even if the source disappears.

That way if you link to something on Imgur or whatever, and then it gets deleted on the host, you still have the image here.

You know, I could actually test that. I’ve linked to images I uploaded to Shutterfly, and I can easily delete them there and see if that breaks the image in a post.

ETA: Apparently that’s a bad test. If you delete a photo from your album, they actually keep it in their database, so it doesn’t actually go away. I might have to test one of my really old Imgur uploads instead.

---

<div class="post-metadata">

**Author:** ![TroutMan](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/troutman/32/6721_2.png) [@TroutMan](https://boards.straightdope.com/u/TroutMan)\
**Post date:** [November 18, 2026, 1:03am UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/19 "2026-11-18T01:03:34Z")

</div>

Ah, thanks for that link. That led me to this issue, which suggest you can disable that using setting `download_remote_images_to_local`. I’m willing to sacrifice a permanent copy of images if it gets us the onebox back.

> **[How to disable links turn upload?](https://meta.discourse.org/t/how-to-disable-links-turn-upload/253148/5)**
>
> If you don’t want external files being automatically uploaded to your forum, disable the download remote images to local in the admin settings. 🙂 Note that this setting only affects images, and Discourse never automatically downloads remote files...

---

<div class="post-metadata">

**Author:** ![Atamasama](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/atamasama/32/12961_2.png) [@Atamasama](https://boards.straightdope.com/u/Atamasama)\
**Post date:** [November 18, 2026, 1:07am UTC](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160/20 "2026-11-18T01:07:09Z")

</div>

Aha, test confirmed!!!

Look at this post:

[https://boards.straightdope.com/t/larson-comic-whats-the-funny/990434/184](https://boards.straightdope.com/t/larson-comic-whats-the-funny/990434/184)

In the preview you should see an Imgur error, because I deleted the image (if it loads a preview at least). But click and look at the post. The picture is still there! (It’s the picture of two Vikings from a _Far Side_ comic.) The preview in this post is broken because it’s trying to create another thumbnail from the source, and the source is gone. But go to the actual post, and the picture is still there because it is stored on the Discourse server from when I first posted it. That’s proof that they are in fact being locally stored. You can also click the picture of the Vikings and you’ll get an error because the image isn’t on Imgur anymore.

ETA: I don’t see a preview in this post even though it was showing up in my editing window. Weird! Maybe it’s the same “can’t include images” error at work.

[Next page](https://boards.straightdope.com/t/cant-post-images-at-all-anymore/1035160.md?page=2)
