# Upload files/images directly to Airtable

**URL:** <https://community.weweb.io/t/upload-files-images-directly-to-airtable/9288>\
**Category:** How do I?\
**Created:** [June 23, 2024, 10:23pm UTC](https://community.weweb.io/t/upload-files-images-directly-to-airtable/9288 "2024-06-23T22:23:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![thisismetrying](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/thisismetrying/32/2069_2.png) [@thisismetrying](https://community.weweb.io/u/thisismetrying)\
**Post date:** [June 23, 2024, 10:23pm UTC](https://community.weweb.io/t/upload-files-images-directly-to-airtable/9288/1 "2024-06-23T22:23:16Z")

</div>

Is there a way to bypass weweb’s cdn to upload directly to airtable?

I’ve tried converting files and images to base64 and adding the result to a long text field in airtable. Then, I convert it to url to show on weweb. It works but for smaller files only like less than 100 or 200KB. When I upload more than that, it causes error.

Is there a workaround for this? Is there a way to not use third party file hosting?

Edit: I researched and it will be impractical to use base64. Guess we really need third party hosting.

---

<div class="post-metadata">

**Author:** ![Slavo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/slavo/32/13253_2.png) [@Slavo](https://community.weweb.io/u/Slavo)\
**Post date:** [June 24, 2024, 11:49am UTC](https://community.weweb.io/t/upload-files-images-directly-to-airtable/9288/2 "2024-06-24T11:49:12Z")

</div>

You can’t upload images to Airtable - their API does not allow that.

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [June 24, 2024, 12:14pm UTC](https://community.weweb.io/t/upload-files-images-directly-to-airtable/9288/3 "2024-06-24T12:14:16Z")

</div>

Apparently you can’t as Slavo mentioned. What you could do though, is introduce an “intermediary” to your workflows, such as Supabase’s Storage, Xano’s Storage or an another “storage provider” and only store references to those images in Airtable. There are some nice guides like this one [How to upload images to Airtable using their API | Chinara James](https://chinarajames.com/how-to-upload-images-to-airtable-using-their-api/) on the internet. Even though if you need some more complex usecases, you might want to consider leveling up from Airtable entirely.

---

<div class="post-metadata">

**Author:** ![nico](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/nico/32/12975_2.png) [@nico](https://community.weweb.io/u/nico)\
**Post date:** [February 28, 2025, 6:31am UTC](https://community.weweb.io/t/upload-files-images-directly-to-airtable/9288/4 "2025-02-28T06:31:06Z")

</div>

When working with Base64 encoded files, I’ve found it helpful to use the [htmlcsstoimage.com](http://htmlcsstoimage.com) service along with Zapier or Make. This creates a URL that can then be uploaded to Airtable.