Media Stores

A media store is where your files live — the images your results show, and the data files (JSON or CSV) you build a list from. The store is storage you control; the platform reads from it to fill in results and to import records. Every account starts with a built-in store, so uploads and imports work straight away; connect your own cloud bucket when you’d rather keep the files in your account.

Auto-plays · use Back / Next to step through at your own pace.

Connect a media store

1. Go to Media. The built-in Search Stack Storage store is already there and is the default for new lists.
2. To use your own bucket, click Add Media Store and pick a provider — Azure Blob Storage, Amazon S3 or Firebase Storage.
3. Give the store a name and its connection details, then click Add. Your files stay in your account; the platform only reads what it needs.

Import records from a file

Point a list at a media store and you can build it straight from a data file in that store — a products.json or catalogue.csv becomes searchable records, no code required. Each imported record remembers where it came from, shown by a sync badge on the record, so you can always tell file-sourced records from ones added by hand or over the API.

Edit the file in the console, and re-import automatically

You don’t have to leave the console to change source data. A synced JSON or CSV file can be edited right here, and the list picks up the change. Turn on automatic re-import and the list keeps itself in step with the file: update the file and the records update to match, on a regular check — so “the search is out of date” stops being a chore you have to remember. The import is upsert-only: it adds and updates records, it never deletes behind your back.

Images in results

The other job of a media store is images. Upload a picture against a record (or store it in your bucket) and a resource field can carry its URL, so your results render with thumbnails and posters straight from your own storage. For searching by an image rather than showing one, see Image Search.

A worked example

Say your catalogue lives in a products.json file your team already maintains. You connect the bucket it sits in as a media store, point a products list at that file, and switch on automatic re-import. Now every time someone updates the file, your search refreshes itself — new lines appear as records, edited lines update in place, and each carries a sync badge showing it came from the file. Your search stays current with zero extra steps in your workflow.