You would need to use a linked record field for this, so each URL would appear in its own record in another table.

If you haven’t used linked record fields before, I explain them in depth in my Airtable training course which you can take for free by signing up for a trial membership with LinkedIn Learning.

Note that the course is very outdated because it was created many years ago using one of the very earliest versions of Airtable. It was created before automations even existed, and it was created years before interfaces existed!

However, the core concepts of building a base remain the same to this day — such as working with linked record fields, working with lookup fields, and how to properly structure your base.

Also, if you’re looking for an easy way to automate communicate between AWS S3 and Airtable, your best bet is to use Make’s AWS S3 integrations alongside Make’s Airtable integrations.

If you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread. For example, here is one of the ways that you could instantly trigger a Make automation from Airtable. 

I also give live demonstrations of how to use Make in many of my Airtable podcast appearances. For example, in this video, I show how to work with Airtable arrays in Make.

Hope this helps!

If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

How do you plan on using the URLs? A long text field can include multiple links. Even a regular URL field can technically hold multiple URLs. But multiple URLs in a single field often does not work well for reuse. 

I'm building a price comparison site on WeWeb so I need the images for the search results page and products page and nothing really more than this.

I would also suggest using a linked record - one table with your Products and one table with your Product Images. Then it's nice because you can add additional details about the Product Images in the other table (this one is for the e-commerce site, this one is for marketing campaigns, etc). Then you can create a lookup for the URLs and it will show all image URLs that are linked to that Product.

I'll give it a go today. I've also got the variations linked to the product so just need to see how it's all gonna work out.

Good luck! I've done the same with images for products and variants in Shopify. Scott Rose's links above will likely be very helpful if you get stuck on the lookup aspect.

I've got the method to work but the problem I am facing is that WeWeb is not showing the URL as an image when the data value for the image is coming through lookups. I'm not to sure what the problem is though, however?