Serve Every ACF Image, Gallery, and File Field From the Infinite Uploads Cloud
ACF lets you build real estate listings, staff directories, portfolios, and product catalogs with an image or gallery on every entry. It doesn't manage where those uploads live. Infinite Uploads moves them to cloud storage and a global CDN, with zero code changes because ACF already stores attachment IDs.
150k+
Sites use our WordPress plugins
14 Days
Money-back Guarantee
Advanced Custom Fields and Infinite Uploads: Where Custom Field Media Actually Lives
ACF adds Image, Gallery, File, oEmbed, Repeater, and Flexible Content fields to any post type. Developers use it for real estate listings, staff directories, portfolios, and product catalogs, each entry with its own photos and documents. ACF doesn't manage where those uploads live: every Image and File field saves an attachment to your uploads folder, across hundreds of entries.
Infinite Uploads moves those attachments to cloud storage and serves them from a global CDN. No template changes are needed because ACF fields already store attachment IDs, not file paths. Image and Gallery fields get resized and converted to AVIF and WebP. A File field holding an MP4 gains Video Cloud's adaptive streaming, included on every plan.
Everything else about ACF works exactly as configured: Repeater rows, Flexible Content layouts, options pages, ACF Blocks, and front-end forms built with acf_form() all behave the same. Infinite Uploads only changes where the file physically lives and how fast it loads, not how the field behaves or what get_field() hands back to your template.
Four Problems Infinite Uploads Solves for an ACF-Built Site
Most offload plugins move files and stop. These are the parts that matter when custom fields hold your content.
Every Image and Gallery Field, Optimized Without Touching Code
ACF stores Image and Gallery fields as attachment IDs, so nothing in your theme or field group needs to change. Infinite Uploads intercepts the upload, converts it to AVIF and WebP, right-sizes it, and serves it from the CDN, whichever return format the field uses.
File Fields Holding Video Get Video Cloud Streaming
ACF has no dedicated video field, so developers put MP4s in a File field or a Repeater row. Infinite Uploads recognizes the upload, and Video Cloud encodes it for adaptive streaming in a brandable player, included on every plan, with no separate video account.
Custom Post Types With Hundreds of Entries Stop Filling Your Server
Real estate listings, staff bios, and product catalogs each carry an image or gallery field. Multiply that by hundreds of entries and original uploads pile up fast. Infinite Uploads offloads every one to cloud storage and frees the space back on your hosting plan.
Media Folders Keep Field Images Findable for Editors
A gallery field with hundreds of listing or product photos is hard to browse in the default Media Library grid. Media Folders, search, and sort organize uploads by listing, staff member, or product, so editors find the right image before they build the entry.
Why ACF Developers and Agencies Pair It With Infinite Uploads
Zero Code Because ACF Already Stores Attachment IDs
Image, File, and Gallery fields save the attachment ID no matter which return format you choose. Infinite Uploads changes where that ID resolves to, not how the field works, so field groups and templates stay as built. One click restores files locally if you ever need them.
One Bill for Storage, CDN, and Video
Cloud storage, global CDN bandwidth, and Video Cloud streaming for a File field's video are one monthly price. No S3 credentials to manage, no Vimeo account for a single video, no surprise bandwidth invoice.
One Account for Every ACF Site an Agency Builds
Agencies building real estate, directory, and portfolio sites on ACF connect every client site to one Infinite Uploads account, with unlimited sites, WordPress Multisite support, one invoice, and no per-site cloud credentials to hand off.
What Works, Feature by Feature
Feature
What you get
Image field, any return format
Stores the attachment ID no matter the return format. Infinite Uploads optimizes it to AVIF and WebP, right-sizes it, and serves it from the CDN.
Works
Gallery field (PRO)
Each image in the array is an attachment ID. Every photo in the gallery offloads, optimizes, and delivers from the CDN the same as a single Image field.
Works
File field holding an MP4
Video Cloud encodes it for adaptive streaming and plays it in a brandable player. Included on every plan.
Works, Video Cloud
File field holding a PDF or document
Offloaded and served from the CDN like any other attachment. The ID stored in postmeta is untouched.
Works
WYSIWYG field inline images
Images inserted through the media upload button are standard attachments and offload the same as any post content image.
Works
Repeater and Flexible Content media sub-fields
Each nested Image, Gallery, or File sub-field stores its own attachment ID and offloads independently, no matter how many rows or layouts.
Works
ACF Blocks that render field images
Blocks call get_field() and standard WordPress image functions, so the CDN URL comes through wherever the block outputs it.
Works
oEmbed field (YouTube, Vimeo)
Stores an embed URL, not a file. The video stays on the third-party platform, and Infinite Uploads has nothing to offload.
Stays on the platform
Front-end acf_form() uploads
Submissions upload through the same PHP process as any WordPress upload. Pair with our free Big File Uploads plugin to raise the limit.
Add Big File Uploads
Up and Running in Three Steps
1. Connect Infinite Uploads
Install the plugin, connect your account, and sync. Existing Image, Gallery, and File field attachments move to the cloud. ACF field groups are untouched.
2. Point a File Field at Video Cloud
Upload an MP4 to a File field like any other attachment. Video Cloud encodes it in the background and Infinite Uploads serves it in the branded player.
3. Free Up Local Storage
Once the sync finishes, remove the local copies from Infinite Uploads settings. Your server gets its space back, and every field keeps resolving to the CDN.
Good to Know Before You Switch
An Image or File field returning a URL string resolves the CDN address at render time, not in the database. Switching providers later still works because nothing is hard-coded. A template that builds the uploads path manually instead of using the field's return value bypasses that and keeps pointing at your server.
ACF has no dedicated video field, so most sites use File or Repeater for MP4s. Infinite Uploads treats that upload like any other file: Video Cloud encodes it for adaptive streaming and serves it in the branded player, whether it sits in a single File field or a row inside a Repeater.
Field-level permissions and post restrictions are not the same as a private file URL. Like the rest of the WordPress Media Library, an attachment on Infinite Uploads is reachable by anyone with its exact link, whether ACF restricts the field to editors or not.
How We Tested
- Built a custom post type with Image, Gallery, File, and Repeater fields.
- Uploaded an MP4 to a File field and confirmed Video Cloud encoded it.
- Added an oEmbed field with a YouTube URL and confirmed nothing offloaded.
- Submitted a file through a front-end acf_form() upload as a logged-in user.
- Checked the Gallery field images and the Repeater sub-field image on the front end.
Result: everything worked, no configuration needed.
Frequently Asked Questions
Do I need to change my ACF field settings for Infinite Uploads to work?
No. Image, File, and Gallery fields store the attachment ID no matter which return format you use, and Infinite Uploads only changes where that ID resolves to.
What about Repeater and Flexible Content fields?
Each media sub-field inside a Repeater row or Flexible Content layout stores its own attachment ID, so every nested Image, Gallery, or File field offloads exactly like a top-level one.
Does ACF have a video field?
No, ACF has no dedicated video field. Most sites put MP4s in a File field or a Repeater row, and Video Cloud streams whichever one holds the video, included on every plan.
Will my ACF Blocks still render images correctly?
Yes. Blocks call get_field() and standard WordPress image functions, so whatever URL those functions return, including the CDN URL, is what the block outputs.
What happens to oEmbed fields with a YouTube or Vimeo URL?
Nothing changes. An oEmbed field stores the embed URL, not a file, so the video keeps streaming from YouTube or Vimeo, not your server.
Do front-end submissions through acf_form() work?
Yes, file and image uploads through acf_form() offload the same as any admin upload. Very large submissions still need our free Big File Uploads plugin to clear the PHP limit.
Can I return the field as a URL string instead of an array or ID?
Yes. The CDN URL resolves at render time, not in the database, so switching providers later still works, as long as your template uses the field's return value.
Does this work with ACF options pages, users, or taxonomy fields?
Yes. Image, Gallery, and File fields work the same wherever ACF puts them, including options pages, users, and taxonomy terms, because storage is always the attachment ID.
More Plugins That Work With Infinite Uploads
- Infinite Uploads and Elementor
- Infinite Uploads and WooCommerce
- Infinite Uploads and WPForms
- See all integrations
Try Infinite Uploads Free for 7 Days
No credit card. No cloud accounts. No access keys. Install the plugin, connect your site, and every ACF Image, Gallery, and File field starts moving to the cloud automatically.
Plans from $16/mo. Unlimited WordPress sites included.