# שדה Raw\_email post שומר תמונות כמחרוזות Base64

**URL:** <https://meta.discourse.org/t/raw-email-post-field-stores-images-as-base64-strings/233298>\
**Category:** Product Support\
**Created:** [19 ביולי,‏ 2022,‏ 2:41pm UTC](https://meta.discourse.org/t/raw-email-post-field-stores-images-as-base64-strings/233298 "2022-07-19T14:41:15Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)\
**Post date:** [19 ביולי,‏ 2022,‏ 5:18pm UTC](https://meta.discourse.org/t/raw-email-post-field-stores-images-as-base64-strings/233298/2 "2022-07-19T17:18:25Z")

</div>

> [@Canapin](#):
>
> Apparently, it’s because images in posts sent by email seem to be present as base64 strings in the **raw\_email** field.

This is going to sound a bit reductive, but that’s how images are sent over email. And since we’re storing the `raw_email`… that’s what we store.

Think of it like a 100MB Inbox. Which is a drop in the bucket for most sites.

You can find the storage size with:

```plaintext
select sum(pg_column_size(raw_email)) / 1048576 as raw_email_MB from posts;

```

> [@Canapin](#):
>
> Is there no better way to do so?

We would no longer be storing the `raw_email` in that case… I suppose there’s an argument to made for stripping large base64 content from `raw_email`s over a certain age…

> [@Canapin](#):
>
> Can it impact performances in any way?

Not likely; it’ll sit on disk but should not be referenced unless you look at it.

🤔

---

_[View the full topic](https://meta.discourse.org/t/raw-email-post-field-stores-images-as-base64-strings/233298)._
