Image or File Fields & Hosting

It is important to understand how images or files are stored and specified within Studio.

Where an element has an image or a file field, the value for that field can be specified in several ways:

  1. The Studio supports uploading of local files. The URL of the uploaded file will be used as a value of the field. Moreover, the uploaded image will be available in the project assets and can be reused for another image field so there is no need to upload the same assest twice.

  2. It is possible to select one of the previously uploaded images from the project assets. The URL of the selected asset will be used as a value of the field.

  3. It is possible to provide a URL to an external image or file. Provided URL will be used as the value of the field. The asset will not be uploaded to the Studio but will be validated once at the point of save. The Studio will not be responsible for their availability or content in the future. Here are examples of valid URLs:

    • https://bucket.io/image.png

    • http://images.com/images/123

    • //d3mss.cloudfront.net/assets/1c/logo.jpeg?_src=lvis

    • https://reports.com/weekly_report.xlsx

The Studio ignores leading and trailing whitespace at the URL validation stage and stores URLs without whitespace.

All image field values are validated according to the App Spec.

Beware. Large images or files used by large audiences can incur significant costs.