Where to store image uploads for an Adalo app
Store the file in a storage service and keep only its URL in your collection. If your data already lives in Adalo, write the URL into an Adalo collection; if you already run a backend such as Xano, write it there so your existing permissions apply; if you have neither, a hosted external collection is the fastest route.
Every uploader saves its files somewhere and records an entry you can read back. Choosing the destination is really choosing where the source of truth for that record lives.
Hosted collection: the simplest path
Uploads land in a hosted collection you read from Adalo as an external collection.
- Nothing to configure beyond picking it as the destination.
- No backend to build or maintain.
Adalo collections: keep data in your app
Good when the rest of your app already lives in Adalo collections.
- Connect it once with your app credentials.
- Images then behave like any other Adalo record, sitting beside your existing data.
Xano: when you already have a backend
Pick this if Xano is already your source of truth.
- Uploads are written to your endpoint so existing logic and permissions still apply.
- You avoid keeping a second data store in sync.
Whichever you pick, tag the upload
Pass the record identifier through the uploader URL so every file traces back.
- Tag each upload with the order, listing or profile it belongs to.
- Untagged uploads are almost impossible to reconcile later.
Store the URL, not the file
Collections should hold the https URL of the image, not the binary.
- Keeping the binary near your record data makes lists slow and exports painful.
- Adalo displays images from a URL perfectly well.
Common mistakes and how to diagnose them
Images show in the uploader but not in Adalo.
- Likely cause:
- The stored value is a file name or a relative path rather than a full https URL.
- Fix:
- Store the absolute URL and confirm it opens in a browser.
Images load slowly in lists.
- Likely cause:
- Full-resolution files used as thumbnails.
- Fix:
- Store or serve a smaller variant for list views.
Deleted records leave orphaned files.
- Likely cause:
- Nothing removes the file when the record goes.
- Fix:
- Delete the upload from its destination as part of the same flow, or run a periodic cleanup.
Real example: an inspection app with an existing backend
A field-inspection app already ran its reporting logic in Xano. Writing uploads into a separate store would have meant reconciling two systems every night.
Pointing the uploader at the Xano endpoint kept one source of truth: the same permissions, the same report queries, and Adalo simply read the resulting URLs.
When you need an Adalo expert
Plenty of Adalo issues are straightforward to fix yourself with the steps above. It usually pays to bring in an experienced Adalo developer when the problem sits deeper in the build:
- Files are private and must only be visible to specific users.
- You need signed URLs, expiry or an approval step before images are visible.
- Existing uploads must be migrated from one destination to another without breaking links.
Related guides
How to upload multiple images in Adalo
Adalo Image propertys take one file at a time. Use a hosted multi-image uploader inside a WebView component so users can pick and upload several files at once.
Why is my Adalo app slow?
The common causes of a slow Adalo app, heavy lists, relationship filters, oversized images and unnecessary data, and what to change for each.
How to structure collections for an Adalo app
Field types, relationships and naming rules that keep an Adalo app fast to filter, easy to change, and painless to connect to an API later.
Frequently asked questions
Can I change the destination later?
Yes, from the uploader's data destination settings. Existing uploads stay where they were written.
Can I delete uploads?
Yes, from the uploads list inside the uploader, or from your own backend if that is the destination.
Should images live in the Adalo collection itself?
Store the URL in the collection and keep the file in storage, that keeps lists fast.
Are uploaded files public?
By default, a plain https URL is reachable by anyone who has it. Private files need signed URLs.
What file size should I allow?
Enough for a phone photo, with compression on. Uncapped uploads on mobile data fail often.
Webnux Tools is an independent product by Webnux Ltd. It is not affiliated with, endorsed by, or sponsored by Adalo, Inc. Adalo is a trademark of Adalo, Inc.