C Clipperry
Features Install Pricing Alternatives Get it free

The clipper test page

Last updated 14 October 2026 · Works with any clipper

Comparison articles are mostly guesswork, because clippers behave differently on different pages. This page takes the guesswork out: it's one page containing the content that breaks clippers. Clip it, paste it into your editor, and compare what you got against the expected Markdown printed underneath each test.

How to use it: install or open the clipper you're evaluating → clip this whole page → paste into Notion, Obsidian or any Markdown editor → work through the checklist at the bottom. Five minutes, real evidence, no marketing.

It's fair to say this page is published by the people who make Clipperry, so treat it with the appropriate suspicion — and then run your current clipper against it, which is the only test that actually matters. If your tool passes, you don't need us.

Before you start

  • Use the same destination for every tool you test (all into Obsidian, or all into Notion) so the comparison is fair.
  • Clip the whole page, not a selection — clutter stripping is half of what you're testing.
  • Keep the raw Markdown visible. Rendered output hides exactly the errors you're looking for.

Test content

Test 1 — A table with a blank cell

The important one. Row three has no value under Seats, so a clipper that drops empty cells will shift Priority one column to the left.

PlanPriceSeatsSupport
Free$01
Team$125Email
Business$29Priority

Pass if: every row has four columns, and Priority sits under Support with Seats left empty.

| Plan     | Price | Seats | Support  |
|----------|-------|-------|----------|
| Free     | $0    | 1     |          |
| Team     | $12   | 5     | Email    |
| Business | $29   |       | Priority |

Test 2 — A wide table

Tests header detection and whether long tables survive without truncation.

RegionQ1Q2Q3Q4Total
Europe1,2401,3101,5021,6885,740
Asia-Pacific9801,0451,1901,3554,570
North America1,6101,5881,7021,7446,644

Pass if: the header row arrives as a header (not as the first data row), and all six columns are present on every row.

Test 3 — Code blocks with language tags

The language tag is what makes syntax highlighting work. If it's lost, the code is still readable but the note is much less useful.

const clipped = articles
  .filter((a) => a.unread)
  .map((a) => ({ ...a, savedAt: Date.now() }));
def normalise(rows):
    return [r for r in rows if r.get("published")]

Pass if: the block above is fenced with ```javascript (or ```js) and the one below with ```python — not bare ``` fences, and not indented code.

Test 4 — Inline formatting inside a heading

Headings that contain code and emphasis are a common place for escaping mistakes — the backticks often survive as literal characters.

Using Array.prototype.flat() instead of recursive reduce

Pass if: the heading keeps its backticks and asterisks as Markdown formatting, with no stray escape characters like \`.

Test 5 — Nested lists

Indentation is easy to flatten, which destroys the structure.

  • Extraction stage
    • Readability scoring
      • Paragraph density
      • Link-to-text ratio
    • Clutter rules
  • Conversion stage
    • Table element parsing
    • Code language detection

Pass if: three levels of indentation survive, and the second top-level bullet is a sibling of the first, not a child of it.

Test 6 — Blockquote with a link and inline code

The cleanest test is to clip a page you actually care about and read it a week later. If you have to open the original to understand your own note, the clip failed. See the table guide for the | counting trick.

Pass if: the > prefix survives, the link keeps its URL, and the inline code stays inline.

Test 7 — Page furniture that should not appear

Everything above is content. This page also has a navigation bar, footer links, a copyright line and a legal disclaimer — none of which should end up in your note.

Pass if: your clipped note starts at the heading "The clipper test page" and ends before this page's footer, with no menu items, no disclaimer and no copyright line.

Scoring checklist

#CheckWhy it matters
1 Table columns stay aligned when a cell is blank The silent failure — a table that lies
2 Wide table keeps its header row Otherwise the first data row becomes the header
3 Code fences carry a language tag No tag, no syntax highlighting
4 Formatting inside headings survives Escaping bugs are common and easy to miss
5 Nested list indentation is preserved Flattened lists lose their meaning
6 Blockquotes and inline links survive Citations and sources are usually links
7 No navigation, footer or cookie text Clutter is why clipped notes feel unusable

Six or seven passes — your clipper is good, keep it. Four or five — it works, but you're doing manual cleanup. Three or fewer — the time you spend fixing clips probably exceeds the time clipping saves.

How Clipperry scores here

We built the test content around the failures we kept hitting ourselves, so naturally we think we pass. Don't take our word for it — run it. Clipperry is a Chrome extension that clips to Notion, Obsidian or plain Markdown, extracts in your browser rather than on a server, and has a free tier of 50 clips a month so you can compare before paying anything.

If your current tool already scores six or seven, we'd genuinely rather you kept it — switching tools costs more than it saves at that point.

Install free for Chrome

Related guides

  • Copy a table from a website into Markdown
  • How to save a web page as Markdown
  • How to save a web page to Obsidian
  • How to save a web page to Notion
  • Web clipper alternatives compared
C Clipperry
Privacy Policy Terms of Service hello@clipperry.com
Markdown guide Obsidian guide Notion guide Table guide Clipper test page Alternatives

Clipperry is not affiliated with, endorsed by, or sponsored by Notion Labs, Inc. Notion is a trademark of Notion Labs, Inc. Obsidian is a trademark of Dynalist Inc. Other products named on this page are trademarks of their respective owners.

© 2026 Clipperry. All rights reserved.