Articles in this section

Event Image Requirements

Image types/compression

All imagery should be supplied as JPG or PNG. If retina-sized images cannot be supplied, then images must be supplied at the display size at a minimum. Reasonable compression should be applied to imagery before being uploaded to the CMS. This will help improve loading times for users. Any resizing and cropping should be done before uploading to the CMS as at this stage we do not support image editing functionality.

Seller Logo

Metadata name: image
Where it's shown: CMS image and digital wallets
Preferred size: 660 x 660, 200 dpi/ppi

The seller logo should be a square image in a JPEG or PNG format. 

Screenshot 2025-05-16 at 4.28.26 PM.png

Best Practice

If your seller image is appearing blurry, check the image size. Alternatively, if you are using a smaller image size (i.e 277x277), you can add ?shrinkonly&sizex=660 to the end of the image url in the seller metadata. After doing so, click refresh on your screen and it should no longer appear blurry.

image (12).png

Event list image

Metadata name: image_profile
Where it's shown: List view, CMS image, Cart image, and digital wallets
Preferred size: 1704 x 1704 pixels, 72 dpi (3 x the max display size)

Our default layout for the event listing page is to have each event displayed vertically one above the other with an event consisting of a left-aligned image, a centered body of text and an action button aligned to the right.

The display size for the Event Listing Thumbnail/image profile in this layout is 152 x 152 pixels when displayed on desktop. When the site transitions to mobile (600 pixels and below), the Event Listing Thumbnail display size increases to 568px. Both sizes have an aspect ratio of 1:1. For this image to support retina devices, it needs to be supplied at an ideal size of 1704 x 1704 pixels (3 x the max display size).



Event detail image

Metadata name: image_cover
Where it's shown: Top of the event detail page
Preferred size: 2904 x 1314 pixels, 72 dpi (3 x the max display size)

The display size for the event detail image is 744 x 336 pixels when displayed on a desktop/full screen. When the site transitions to tablet (1000px down to 601px), the event detail image display size increases to 968 x 438 pixels. It has an aspect ratio of 2.2:1.

For this image to support retina devices, it needs to be supplied at an ideal size of 2904 x 1314 pixels (3 x the max display size). This size works across all screen sizes.

Please note the above requirements are the default for our event page. The event page supports any image size and will maintain its aspect ratio. Be warned this can cause very tall images to be displayed, that is why we specify default values.



Event configuration image settings

Within the Configuration menu on the event there are 2 image settings available.

  1. Alternative Text - this field is the ability to add alternative text for vision-impaired customers, screen readers, and search engines. It is used for the <img alt=""> attribute for the event list image and event detail image. At this time the alternative text set here serves as the alternative text for both images, regardless of if the images are different.
  2. No Cropping - by checking this box, the e-Commerce site will always show the full image without cropping it. This maintains the full original image without cropping any of it. This is often required for licensed or copyrighted works of art.



Confirmation page image

Where it's shown: final confirmation page of eCommerce purchase
Metadata name: see the article How To Update the Confirmation Image Shown On the Website Confirmation Page
Preferred size: 4296 x 1344 pixels, 72 dpi (3 x the max display size)

The display size for the Confirmation Image is 1432 x 448 pixels. It has an aspect ratio of 3.2:1. For this image to support retina devices, it needs to be supplied at an ideal size of 4296 x 1344 pixels (3 x the max display size). This size works across all screen sizes.



 

 


Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.