Skip to content
bobob

Iframe Viewer

Preview URLs inside common viewport frames and copy basic iframe markup.

Runs in your browserNothing you type is sent to a server.

Input and result

What you type is kept in this browser only. Reopen to restore your last run.

Use cases

  • Preview public pages in common viewport frames
  • Copy iframe markup
  • Check frame blocking behavior

Examples

Desktop
1440 x 900
Useful for full-width web app checks.
Tablet
834 x 1112
Checks medium breakpoint behavior.
Mobile
390 x 844
Good for common mobile layout checks.

Common mistakes

  • Iframe Viewer can still fail when the pasted input shape differs from https://www.bobob.app.
  • The output should be reviewed in the target web workflow before reuse.
  • Browser-local processing does not make sensitive production data safe to paste.

Before you copy

  1. 1Compare the output against the original input before copying.
  2. 2Remove secrets, customer data, and one-off environment values.
  3. 3Continue with url-parser if the result needs another validation step.

Sources

  • If it will not load, the site usually blocked it

    It is the other site refusing, not your browser. There are two ways to refuse: the X-Frame-Options response header (RFC 7034) and Content-Security-Policy's frame-ancestors. When both are present, current browsers follow frame-ancestors.

    Basis: RFC 7034

  • Banking and sign-in pages are blocked by design

    Refusing to be framed is how a site stops clickjacking - an attacker laying its page invisibly over another to steal clicks. Such a page failing to load is correct behaviour, not a fault.

    Basis: Intended security behaviour

FAQ

Why does a site refuse to load?

Some sites block framing with X-Frame-Options or Content-Security-Policy. That is a security feature.

Is the entered URL stored?

No. The preview runs in the browser and the tool does not persist entered URLs.