Soon You'll Need a CDN
One of the best features of Airtable is the ability to drag images, files, and even videos (i.e., digital artefacts) right into an attachment field. When you do this, Airtable makes a copy of your image and stores metadata about the image into your base. It also quietly moves the copy of your image to its content delivery network (CDN). The URL to your image has been openly accessible providing a wonderful way to share access to your assets For almost eight years, this has been possible but that’s going to change in significant ways later this fall.
Long Time Coming
I predicted this would happen in 2019. They warned us then and they are giving you almost a year to make plans. A lot of folks complained here, but this change is most certainly going to happen and it is in everyone’s best interest.
Now that Airtable has officially announced new specifications for its CDN, any solutions that depend heavily on images that need to be accessed outside the Airtable UI will probably require that you host them in your own CDN.
What’s a CDN?
Cloudflare provides one of the better definitions:
A content delivery network (CDN) refers to a geographically distributed group of servers which work together to provide fast delivery of Internet content. A CDN allows for the quick transfer of assets needed for loading Internet content including HTML pages, javascript files, stylesheets, images, and videos. The popularity of CDN services continues to grow, and today the majority of web traffic is served through CDNs, including traffic from major sites like Facebook, Netflix, and Amazon.
Airtable, of course, has its own CDN to provide access to the images and files you upload to attachment fields. The intent of this CDN is for it’s paying customers; not as a global hosting server. If you need to host your Airtable-bound digital artifacts, you’re going to need to essentially replicate Airtable’s CDN, so you might want to read on.
Thanks Google Drive!
One might think that Google Drive, or other services such as DropBox or Box will host these files for me, but that could be a mistake. These services don’t want to be your CDN any more than Airtable does. They include ToS clauses that allow them to throttle open access to your documents despite being fully shared to the open Internet.
One Approach
There are many ways to create a CDN for your attachment files. In fact, Cloudinary is an ideal ready-made CDN that also provides many features for sizing and rendering images in custom formats and styles. However, it’s not a magic bullet and the pricing might be a little steep depending on your needs.
The complex part requires that you create some sort of an integration that pulls (or pushed) your attachments from Airtable (perhaps using the API or script automation) and upload yet another copy into your CDN environment. If you have a serious commitment to attachments, this could be a sizeable challenge. There’s also the issue of keeping your CDN updated in near-real-time, a key requirement that is more easily addressed with Firebase.
These complexities may not be easy to build depending on your selection of a premade SaaS CDN solution. And, you might also get lucky with Zapier or another glue-factory approach. Experiment a little and see what works best for your situation.
I have already helped a few friends design an approach that uses Firebase, a Google Cloud Platform service that is very fast and provides a generous free tier and an integrated CDN.
WARNING - CDNs are not universal in features. Some are globally distributed while others provide localized servers in your country. The costs vary greatly as well. And it also depends on your hosting and delivery requirements.
Hi @Thibaud_Donzier, @Bill.French ,
I’m already a miniExtensions Customer but I don’t have (yet) an account at CLOUDINARY so I haven’t tried it yet because I’m currently trying to build a reproduction of the Google Cloud 
At Firebase experience beginning, it filled my 3rd screen with ‘awesome’ :winking_face: logs and not very easy to interpret but I still have a few days left not too busy at work outside my own Airtable activities to try to finish and publish some kind of report to share with you for better or for worse, in the state I will have reached. If I can do it in this small remaining time.
About the miniExtension (ME) you are showing, I don’t see where I could automatically retrieve the URL (an URL pointing to Cloudinary of course) of the image saved (transformed) in Cloudinary at the end of the work done by both ME and Cloudinary, without additional means (which ones?) to what ME offers.
However it seems mostly important to me that if an image saved in an Attachment Field of Airtable reaches Cloudinary thanks to ME, when the image is returned processed (or not) from Cloudinary, its reference URL should be written in an URL Field of Airtable, in order to be able to subsequently use the image saved in Cloudinary by its reference URL in an App that is neither Airtable nor airtable’s Shared View. (a built-on-top-of Airtable API frontend App e.g.).
This ME is no longer maintained by its DEV, so it will probably not evolve in this direction.
oLπ
