Does it execute the embed code?
No. The Embed Code Cleaner only cleans the pasted snippet as text. It never runs, renders, or hosts the embed.
Can it remove junk from widget snippets?
Yes. It strips common noisy or risky attributes and script fragments wherever the cleanup is deterministic and safe.
Does this tool upload my code anywhere?
No. The Embed Code Cleaner runs fully in your browser, so your snippet is never uploaded to any server.
Is the Embed Code Cleaner free?
Yes. It is completely free to use, with no account, no sign-up, and no upload.
Does it validate that the embed will work?
No. This is a cleanup tool, not a validator. It tidies the markup but does not confirm the embed renders correctly on a live page.
Will my YouTube or Maps iframe survive the cleaning?
Yes. The iframe is kept with the attributes an embed needs, while the srcdoc attribute and every on* event handler are removed. What comes back is the same embed with the executable parts taken out.
What does the tool actually keep?
Plain HTML embed markup. A Twitter or Instagram embed, for example, is a <blockquote> with a class, some text, and a link, and all of that survives, with the loader script removed. Headings, paragraphs, lists, images, links, and media elements survive as well. Iframes and scripts do not.
Will my X or Instagram embed still render after cleaning?
No. Those embeds are a static <blockquote> plus a widget script that replaces it with the real card. The script is removed, so what you get back is the fallback markup: a quoted block of text with a link. That is fine if you wanted a clean citation and not fine if you wanted the card.
Why did my inline styles disappear?
The style attribute is removed from every element before sanitizing, along with srcdoc and every on* event handler. Embed snippets often carry sizing in style="border:0;width:560px", and it does not come back. Set width and height as attributes instead, which are on the allow-list and survive.
Is this a safe sanitizer for user-submitted HTML?
The underlying library, DOMPurify, is a serious sanitizer and it is doing real work here. The tool is not a security control, though, because it depends on a person pasting markup into a page. If you accept HTML from users, sanitize it on the server or at render time, in code, on every request, and treat this page as an inspection aid.
Is the snippet uploaded or executed?
Neither. The markup is parsed as inert text and cleaned in your browser. The embed is never inserted into a live document, so no script runs and no request is made to the embed's host.