Airtable File Storage

Durable Airtable Attachment URL Storage on a Global CDN

External file storage for Airtable attachments with CDN delivery.

Airtable attachment URLs are not stable. The URLs returned for attachment fields are temporary signed links that expire after a few hours, which is fine inside the Airtable UI but breaks the moment you reference them anywhere else — an external site embedding the image, an email template, a static-site generator pulling from Airtable as a CMS, or another app that cached the link yesterday. cdn22.net fixes this by giving each attachment a permanent CDN URL you store back in Airtable, so downstream systems point at a link that doesn't rot.

The pattern is a mirror-on-create automation. In Airtable Automations, trigger "When a record matches conditions" (e.g. an attachment field is not empty and the permanent-URL field is empty), then run a script step that reads the attachment's temporary URL, fetches the bytes, and uploads them to cdn22.net via the three-call flow — POST /v1/files/{folderId}, PUT to the presigned URL, POST /v1/files/confirm-upload — using your raw API key in the Authorization header.

Write the returned permanent CDN URL into a separate long-text or URL field on the same record. From then on, every integration reads that stable field instead of Airtable's expiring one. The scripting extension works the same way for bulk-backfilling an existing base.

This matters most when Airtable is acting as a lightweight backend: a marketing site rendering a gallery from an Airtable grid, a directory app showing logos, a content calendar feeding social tools, or a product catalog syncing to a storefront. Those all need URLs that survive longer than an afternoon. There's a secondary benefit too — Airtable's per-record and per-base attachment storage counts against your plan, while mirroring large originals to cdn22.net lets you keep a thumbnail in Airtable and the full-resolution asset on durable CDN-backed storage, billed as prepaid credits per GB rather than rolled into a per-seat Airtable plan.

For attachments that shouldn't be public, upload them private and store a reference instead of a public link, minting signed URLs when an authorized app needs them. cdn22.net doesn't replace Airtable as your database — it's the durable, addressable home for the files Airtable only holds temporarily. If you're planning Airtable file upload storage across a wider app, see the broader cloud file storage API, CDN-backed file storage, and document storage pages.

Airtable attachment migration workflow

Migrate Airtable Attachments to Durable CDN Storage

Here is the concrete workflow to move off expiring Airtable attachment URLs and store Airtable attachments on permanent, CDN-backed Airtable file storage. Run it as an Airtable Automation script step for new records, or from the scripting extension to bulk-migrate an existing base.

  1. Read the Airtable attachment URLs

    In your script step, read the attachment field on the record. Each attachment exposes a temporary Airtable attachment URL and a filename — that expiring signed link is exactly what you are migrating away from.

  2. Fetch and upload to cdn22.net

    Fetch the bytes from the temporary URL, then run the three-call upload: POST /v1/files/{folderId} for a presigned PUT URL and file id, PUT the bytes, then POST /v1/files/confirm-upload with {ids:[id]}. The Authorization header is your raw API key (no Bearer prefix). See the cloud file storage API for the full reference.

  3. Write the permanent URL back

    Store the returned permanent CDN URL (https://cdn.cdn22.net/{id}) in a separate URL or long-text field on the same Airtable record, or in your app's own database. Every downstream integration now reads that stable Airtable file storage URL instead of the expiring one.

  4. Keep sensitive attachments private

    For attachments that should not be public, upload them as private files and store a reference instead of a public link. Mint a short-lived signed URL (GET /v1/files/signed/{id}, 10-minute default) only when an authorized app or viewer needs access.

Benefits With No Complexity

Global CDN delivery

Your files are served from 450+ edge locations worldwide.

Edge-cached worldwide

Files are cached close to your users for fast delivery.

Signed-URL security

Private files stay protected with time-limited access.

What You Get

Unlimited files

Upload as many files as you need.

Unlimited storage

There is no storage limit.

Public + Private storage

Private files are fully secured.

CDN ready links

Upload directly to 450+ edge locations worldwide.

Prepaid credits

No subscription. Pay only for the storage and bandwidth you use.

More coming soon

We have plenty of features coming!

How cdn22.net Works

1. Upload

Create a project and upload your first file.

2. Copy

Copy the CDN link.

3. Use Anywhere

Paste and enjoy the blazing speed.

Why Developers Choose cdn22.net

A Better Way to Store & Deliver Files

Airtable AttachmentsCloudinaryAmazon S3cdn22.net
Permanent (non-expiring) file URLs
Global CDN delivery
Mirror-on-create via Automations/scripts
Offloads attachment storage from your plan
Prepaid credits (per-GB, not per-seat)
Private files with signed URLs

Calculate Your Needs

Storage

0GB

Egress

0GB

CDN Bandwidth

0GB
Total: $0.000/month

Start Airtable Storage

  • Global CDN delivery
  • Edge-cached worldwide
  • Signed-URL security
  • Unlimited files
  • Unlimited storage
  • Public + Private storage
  • No subscription — prepaid credits keep spend predictable
Start Airtable Storage

Frequently Asked Questions

Why do Airtable attachment URLs expire?
Airtable returns temporary signed URLs for attachments that expire after a few hours. That's fine inside Airtable but breaks any external site, email, or app that cached or embedded the link.
How do I create permanent URLs automatically?
Build an Airtable Automation that triggers when an attachment field is filled, then a script step fetches the attachment and uploads it to cdn22.net (POST /v1/files/{folderId} → PUT presigned URL → POST /v1/files/confirm-upload) and writes the returned permanent CDN URL into a separate field on the record.
Can I backfill an existing base?
Yes. Use the scripting extension to iterate records with attachments and run the same upload flow, writing each permanent URL back. After that, your integrations read the stable field instead of Airtable's expiring one.
Does this also reduce my Airtable storage usage?
It can. Mirror full-resolution originals to cdn22.net (billed as prepaid per-GB credits) and keep only a thumbnail or reference in Airtable, so large files no longer count fully against your per-base attachment storage.
Can I serve migrated Airtable attachments over a CDN?
Yes. Every file you upload gets a permanent Airtable attachment CDN URL served from a global edge network, so images and documents you mirrored out of Airtable load from the nearest location worldwide instead of relying on Airtable's expiring links.
How do I keep some Airtable attachments private?
Upload those files as private so no public URL is created, then mint a signed URL (GET /v1/files/signed/{id}, 10-minute default) only when an authorized app or viewer needs the file. Public and private attachments can live side by side in the same project.
Is there a file-size limit for the attachments I migrate?
cdn22.net is built for large originals that would otherwise bloat your Airtable plan — mirror full-resolution files to durable per-GB storage and keep only a thumbnail or reference in Airtable if you like. Billing is prepaid credits per GB, so migrated attachments draw down credits rather than a per-seat plan.
General Questions
Is there a subscription?
No. cdn22.net uses prepaid credits, so storage, bandwidth, and API usage are deducted from your balance as you go. The app explains the payment step before uploads are enabled — no monthly subscription and no per-user fees.
What is cdn22.net?
cdn22.net is a developer-first file platform that makes it simple to store, secure, and deliver files globally. It provides signed URLs, public/private access, and an API-first design so you can integrate file delivery into any app without the usual complexity.
How does billing work?
cdn22.net uses prepaid credits. As you use storage, bandwidth, and API requests, credits are deducted daily. When your balance runs low, we automatically recharge it using your saved card. If an auto-recharge doesn't go through, your files and links stay put — you simply update your payment method or top up manually to keep going. No monthly subscriptions — just simple usage-based pricing.
How secure is my data?
All files are encrypted at rest and in transit. You can use signed URLs for private files, control access with permissions, and rely on enterprise-grade infrastructure for data protection.

Related

cdn22.net
Copyright © 2026
All rights reserved
ContactGuidesGlossaryStatusLegal