Your page, exactly as you made it

PubSpace serves the bytes you publish. Scripts run, charts draw, buttons and filters work. Nothing is sanitized, rewritten, minified or boxed into a sandbox, so the link you send a client or your CEO opens the page you saw on your own screen.

What PubSpace adds, and nothing else

• A few tags in the page's <head>: the page id, a do-not-index tag (unless you opt the page into search on Pro), and share-card tags so the link previews in Slack and email.
• A thin bar along the bottom that says the page is published with PubSpace, with a link to claim a space and a Report link readers can use to flag the page to us. Pro can hide it.
• The comments layer, only on pages where you turn comments on. It lives in its own shadow DOM, so your styles and click handlers never see it.

What it doesn't do

Hosts that sanitize HTML remove scripts and inline handlers, so charts and buttons stop working. Hosts that wrap a page in a sandboxed iframe can block saved settings, downloads, popups or forms. PubSpace does neither. It doesn't rewrite links, move or inline your CSS, or reformat your markup either.

Test it yourself

The test file checks itself: inline scripts, onclick handlers, the page's own document listeners, localStorage and sessionStorage, canvas charts, inline SVG, CSS grid and animation, form handlers, non-English text and emoji, web components and dialogs, generated downloads, script order, and ES modules. Open it on your computer, then publish it and open the link. Every check should pass in both places, and the result line shows when PubSpace served it.

Or ask your agent: Publish https://pubspace.ai/samples/fidelity-test.html to PubSpace and send me the link.

How it stays that way

Any change to how PubSpace stores or serves pages is checked by comparing the served page with the stored one, byte for byte, in a real browser. The only differences allowed are the ones listed above.