The HTML renderer can load cross-origin images
without extra configuration.

CanvasKit requires that the app gets the bytes of the encoded image.
There are several ways to do this, discussed below.

Host your images in a CORS-enabled CDN.

Typically, content delivery networks (CDN)
can be configured to customize what domains
are allowed to access your content.
For example, Firebase site hosting allows
specifying a custom Access-Control-Allow-Origin
header in the firebase.json file.

Lack control over the image server? Use a CORS proxy.

If the image server cannot be configured to allow CORS
requests from your application,
you may still be able to load images by proxying the requests
through another server. This requires that the
intermediate server has sufficient access to load the images.

This method can be used in situations when the original
image server serves images publicly,
but is not configured with the correct CORS headers.

Examples: