Embedded webview


Add support for embedded browser / web view.

Use Case
Xanthar is a graphic designer who is creating graphics for a medical imaging company. He’s created a plugin that pulls in x-rays he receives, adds a layer of vector graphics over them and then exports the artboard to SVG in an HTML page on the local intranet.

He has automated some of it but when the doctor wants to see the export they have to open a browser, copy a link from the plugin and paste that link into the browser.

Xanthar found the new web view API and is able to open the exported HTML page right in XD.

Use Case
Lily is a botanist, computer scientist and teacher from India that is using XD to create artificial flowers in vector format from her growth branching algorithm.

She released her first plugin one month ago and her students are starting to use it but have been emailing her on how to use it. She decides to write instructions for her users in Word and exports it to HTML. She put the instructions online but the internet goes down multiple times a day so she wants to include the web page with her plugin.

She finds out about the web view and when her users click on the help icon the help page loads right in her plugin.


We’ve received this request from other partners as well. We will discuss this internally and report back here.

1 Like

Thank you for suggestiong this - web views are an essential feature for UXP (not just for XD)!
My CEP panel BeatEdit for Premiere Pro has a waveform preview and audio payer, for example, and Squash & Stretch for After Effect has a build-in animation preview. Both will not be doable without a web view.

So if the plan is that UXP replaces CEP in the long term, please make sure you provide a web view if you don’t want to kill popular extensions. If you don’t plan to support web views, please explain how I should migrate those extensions.

The animation preview of Squash & Stretch involves sound (and the waveform audio player of BeatEdit, too) so note that audio support for the web view is also crucial.

Audio playback is also needed by QuickImporter for Ae, Au, Pr.


I think this would also ease some of the development pressure on the Adobe team. My understanding is since UXP is not built on something like Electron (basically just a web browser), but is instead using web technologies to define the user interface, being rendered using proprietary code, it’s going to be very hard to make sure the UXP runtime is in sync with the latest web technologies.

A lot of plugins currently written on CEP make use of these modern technologies to create high-quality user interfaces and innovative features. If the plugin authors are limited to a fairly small scope of HTML, I think their ability to innovate and help push Adobe products to new limits would be severely limited.


Including @afuchs for visibility. We’ve got a couple of helpful feedbacks on this webview feature request

1 Like

I think you’ll be surprised at how wide the HTML/CSS coverage already is, and it’s getting wider.


Good to hear! Excited to keep following these updates.