Own Copy — offline web clipper by Quiet Tools Studio
Save the article you are reading to your own disk as Markdown — text and pictures. No account, no server, nothing sent to us.
1 User1 User
Extension Metadata
About this extension
<p><strong>Own Copy saves the article you are reading to your own disk.</strong>
Not to a bookmark, and not to somebody's server. The text, the pictures and the
metadata land in a folder you chose, as Markdown you can read in ten years.</p>
<h3>Why another clipper</h3>
<p>The popular ones each fail in one of four ways, and we built this to avoid all
four:</p>
<ul>
<li><strong>They upload the page.</strong> Saving an article sends it to a
company's server, along with what you read and when. Own Copy has no
server to send it to, and no account to tie it to.</li>
<li><strong>They lock you out of your own notes.</strong> A login breaks, a
captcha loop starts, and the archive you built becomes unreadable.
Own Copy has no account, because there is nothing to sign in to.</li>
<li><strong>They save the headline instead of the article.</strong> Or they
ask you to go online to save a page you are already reading. Own Copy
extracts the article, strips the navigation, ads and sidebars, and writes
the whole thing.</li>
<li><strong>They save a link to the pictures instead of the pictures.</strong>
The file looks complete until the train enters a tunnel, or the site
moves its images, and then the article is text with grey boxes. Own Copy
puts the pictures inside the file.</li>
</ul>
<h3>What you get</h3>
<ul>
<li>Markdown with YAML front matter — title, author, source, publication date
— so Obsidian, Notion and Logseq read it back automatically</li>
<li><strong>The pictures inside the file</strong>, so the article is complete
on a train and still complete when the site has moved or deleted them</li>
<li>A standalone HTML file when you want to read rather than edit</li>
<li>Files named after the article, with characters your filesystem cannot
take removed</li>
<li>A subfolder of your Downloads, or ask-me-each-time if you prefer</li>
</ul>
<h3>About the pictures, and the one thing we ask for</h3>
<p>Saving the pictures needs permission for the site you are saving from, and
that permission is the only thing this extension ever asks for. It is requested
when you press save — never at install time — and it names the site. Say no and
the article is still saved, with its pictures as links and a note telling you
how many.</p>
<p>With that setting turned off, Own Copy makes no network request of any kind.
Nothing is ever sent to us: there is no server, no analytics and no account.
The extension talks to the site you are already reading, and to nowhere
else.</p>
<h3>Long pages, and pages with more than one article</h3>
<p>Many sites hold the second half of an article back until you scroll near it.
Own Copy walks the whole page before reading it, so the ending is saved too, and
puts you back where you were afterwards.</p>
<p>A news page is usually one article followed by a feed of others, and nothing
in the markup reliably separates them — both are blocks of prose with a heading.
Rather than guess, Own Copy lists what the page offers and ticks the one you are
reading. <strong>One thing to know:</strong> a feed entry is saved as the text
shown on that page, which for a short brief is the whole thing and for a longer
piece is the opening. The full text lives on the article's own page; open it and
save from there for the complete piece.</p>
<h3>What it will not do</h3>
<ul>
<li>It will not sync, share, or back up to anywhere. There is no "anywhere".</li>
<li>It will not ask for an account, because it has no use for one.</li>
<li>It will not invent an article where there is none. On a search results
page or an app screen it says so, rather than writing a file full of
navigation.</li>
<li>It will not follow a link for you. What gets saved is what the page in
front of you contains.</li>
</ul>
<h3>Permissions, and why each one exists</h3>
<ul>
<li><code>activeTab</code> — read the page you are on, and only after you
click the button</li>
<li><code>scripting</code> — put the extractor into that page</li>
<li><code>downloads</code> — write the file</li>
<li><code>storage</code> — remember your folder and format choice</li>
<li>site access — <strong>not granted at install time.</strong> Asked for one
site at a time, when you save an article whose pictures you want, and
refusable</li>
</ul>
<p>There is deliberately no host permission at install and no
<code><all_urls></code>. The one above is asked for later, site by site,
and only when you save pictures. Own Copy cannot see any page until you ask it
to.</p>
Not to a bookmark, and not to somebody's server. The text, the pictures and the
metadata land in a folder you chose, as Markdown you can read in ten years.</p>
<h3>Why another clipper</h3>
<p>The popular ones each fail in one of four ways, and we built this to avoid all
four:</p>
<ul>
<li><strong>They upload the page.</strong> Saving an article sends it to a
company's server, along with what you read and when. Own Copy has no
server to send it to, and no account to tie it to.</li>
<li><strong>They lock you out of your own notes.</strong> A login breaks, a
captcha loop starts, and the archive you built becomes unreadable.
Own Copy has no account, because there is nothing to sign in to.</li>
<li><strong>They save the headline instead of the article.</strong> Or they
ask you to go online to save a page you are already reading. Own Copy
extracts the article, strips the navigation, ads and sidebars, and writes
the whole thing.</li>
<li><strong>They save a link to the pictures instead of the pictures.</strong>
The file looks complete until the train enters a tunnel, or the site
moves its images, and then the article is text with grey boxes. Own Copy
puts the pictures inside the file.</li>
</ul>
<h3>What you get</h3>
<ul>
<li>Markdown with YAML front matter — title, author, source, publication date
— so Obsidian, Notion and Logseq read it back automatically</li>
<li><strong>The pictures inside the file</strong>, so the article is complete
on a train and still complete when the site has moved or deleted them</li>
<li>A standalone HTML file when you want to read rather than edit</li>
<li>Files named after the article, with characters your filesystem cannot
take removed</li>
<li>A subfolder of your Downloads, or ask-me-each-time if you prefer</li>
</ul>
<h3>About the pictures, and the one thing we ask for</h3>
<p>Saving the pictures needs permission for the site you are saving from, and
that permission is the only thing this extension ever asks for. It is requested
when you press save — never at install time — and it names the site. Say no and
the article is still saved, with its pictures as links and a note telling you
how many.</p>
<p>With that setting turned off, Own Copy makes no network request of any kind.
Nothing is ever sent to us: there is no server, no analytics and no account.
The extension talks to the site you are already reading, and to nowhere
else.</p>
<h3>Long pages, and pages with more than one article</h3>
<p>Many sites hold the second half of an article back until you scroll near it.
Own Copy walks the whole page before reading it, so the ending is saved too, and
puts you back where you were afterwards.</p>
<p>A news page is usually one article followed by a feed of others, and nothing
in the markup reliably separates them — both are blocks of prose with a heading.
Rather than guess, Own Copy lists what the page offers and ticks the one you are
reading. <strong>One thing to know:</strong> a feed entry is saved as the text
shown on that page, which for a short brief is the whole thing and for a longer
piece is the opening. The full text lives on the article's own page; open it and
save from there for the complete piece.</p>
<h3>What it will not do</h3>
<ul>
<li>It will not sync, share, or back up to anywhere. There is no "anywhere".</li>
<li>It will not ask for an account, because it has no use for one.</li>
<li>It will not invent an article where there is none. On a search results
page or an app screen it says so, rather than writing a file full of
navigation.</li>
<li>It will not follow a link for you. What gets saved is what the page in
front of you contains.</li>
</ul>
<h3>Permissions, and why each one exists</h3>
<ul>
<li><code>activeTab</code> — read the page you are on, and only after you
click the button</li>
<li><code>scripting</code> — put the extractor into that page</li>
<li><code>downloads</code> — write the file</li>
<li><code>storage</code> — remember your folder and format choice</li>
<li>site access — <strong>not granted at install time.</strong> Asked for one
site at a time, when you save an article whose pictures you want, and
refusable</li>
</ul>
<p>There is deliberately no host permission at install and no
<code><all_urls></code>. The one above is asked for later, site by site,
and only when you save pictures. Own Copy cannot see any page until you ask it
to.</p>
Rated 0 by 0 reviewers
Permissions and data
Required permissions:
- Download files and read and modify the browser’s download history
Data collection:
- The developer says this extension doesn't require data collection.
More information
- Add-on Links
- Version
- 0.2.1
- Size
- 55.07 KB
- Last updated
- a month ago (Oct 17, 2026)
- Related Categories
- License
- All Rights Reserved
- Version History
- Add to collection