Limited support for shader effects that can be applied to images.

No control over image memory (Image.dispose has no effect).
The memory is managed by the browser behind-the-scenes.

The CanvasKit renderer implements Flutter’s image API fully.
However, it requires access to image pixels to do so,
and is therefore subject to the CORS policy.

Solutions

In-memory, asset, and same-origin network images

If the app has the bytes of the encoded image in memory,
provided as an asset, or stored on the
same server that serves the application
(also known as same-origin), no extra effort is necessary.
The image can be displayed using
Image.memory, Image.asset, and Image.network
in both HTML and CanvasKit modes.

Cross-origin images

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