I use this simple method a few times throughout this site, so that I can pull some custom widgets into a WordPress page and not have to worry about conflicting CSS or messing with HTML escaping in WordPress post content. Then to embed, you could simply pull it in via the standard iframe element.

Lets pretend you uploaded it to the root of your domain, at /widget-A.html. I would be remiss if I didn’t mention the default way to host up an iframe that others can embed simply throw your code into a static HTML file (or generate with server-side code, more on that later), and shove the file onto your publicly accessible host (shared host, VPS, AWS bucket, etc). Generating iframe content server-side & some warnings.Dynamic iframe generation: client-side and inline attributes.This post is a way for me to organize some notes on the topic and keep a list of resources related to iframe embeds, specifically for developers. I personally use iframes somewhat often, but infrequent enough that I often forgot things like “can I force this site’s widget into an iframe?”, or “what is the fastest way to throw this into a publicly accessible iframe embed?”. Especially as concern grows about the amount of invasive tracking and its negative effect on page performance, iframes continue to be an excellent way to force third-party code into sandboxes, where they can’t interact with the host page (unless explicit data passing has been setup).

I feel like iframes are a very under-appreciated part of the web-development world.

Html to embed code generator iframe