// HOW-TO · REPURPOSING

How to share saved articles via Buffer (turn your read-it-later pile into posts, 2026)

Turn unread saved articles into social posts with Buffer: pull them from your read-it-later app, save each as an Idea, add a real take, and queue per platform.

Last verified · 2026-10-23 · by Moe Ameen

Published 2026-08-17 · Updated 2026-10-23

Short answer

To share saved articles through Buffer, open each saved piece from your read-it-later app, click the free Buffer extension (Chrome, Safari, Opera or Edge) and choose Save Idea. In Buffer, replace the auto-pulled headline with your own take, use the AI Assistant to adapt it per channel, credit the source, and schedule a few a week. Buffer has no direct read-it-later integration, and Pocket shut down in 2025.

Key takeaways

Pocket shut down July 8, 2025, and exports ended October 8, 2025.
The Buffer extension is the bridge: Save Idea parks a page for later.
Highlight a line, right-click, choose Buffer and save the quote as an Idea.
Your take is the post. The article is raw material.
Test link placement on your own account instead of trusting a rule.

Most people save far more articles than they ever read, let alone share. The tab you meant to get back to, the newsletter link you starred, the report a colleague dropped in Slack — they pile up in a read-it-later app or a browser reading list and quietly go stale.

Every one of those is a post you did not have to think up from scratch. Sharing them through Buffer turns that backlog from guilt into a steady, low-effort content stream — but only if you do more than paste the link.

The mechanics are simple: Buffer's browser extension lets you send any page straight to a scheduled post or park it on your Ideas board, and its AI Assistant can draft a caption from a short prompt. The part that separates a feed people follow from a link-dump nobody clicks is what you add — your angle, why the article matters to your audience, and honest attribution. This guide walks the full loop: get the saved articles into one place, triage them, capture the good ones in Buffer, write a take instead of a headline, and queue them at a cadence so the pile actually clears.

One honest note up front, because it changes your source: Mozilla shut Pocket down in 2025, so "saved articles" now means whatever you moved to — Instapaper, Readwise Reader, Raindrop, a browser reading list, or plain bookmarks. Buffer does not connect to any of those directly; the bridge is its browser extension, which works from whatever page you have open. This guide assumes you are pulling from a list you already keep.

Consolidate your saved articles into one working list. Before Buffer touches anything, get your backlog into a single place you can scan. Export or open your read-it-later app (Instapaper, Readwise Reader, Raindrop), your browser reading list, or your bookmarks, and skim the titles. The goal is one triage session, not fifty individual "should I share this?" decisions spread across a week. If you were a Pocket user, note that it closed in 2025 and exports ended that October — pull from wherever your saves live now.
Install the Buffer browser extension and connect your channels. Add the free Buffer extension from your browser's store — it supports Chrome, Safari, Opera, and Edge — and sign in. Confirm the social channels you want to publish to are connected in your Buffer account first, because the extension's composer pulls that channel list when you go to schedule. Pin the icon to your toolbar so it is one click from any article page.
Triage: keep only the articles worth a post. Saved is not the same as post-worthy. Go through your list and keep an article only if you can answer one question about it: what does my audience get from this that they would not get elsewhere? Drop anything off-topic for your lane, anything already dated (a "this week in X" piece you saved a month ago is dead), and anything you have not actually read. Sharing a headline you skimmed is how you end up recommending something that says the opposite of what you assumed.
Save each keeper to Buffer as an Idea, not straight to the queue. With the article open, click the Buffer icon and choose "Save Idea" rather than "Create Post." This lands the page in your Ideas, inside Buffer's Create space (its Board view lets you sort ideas into groups), where the link, title, and any image are captured as a draft you develop before it publishes. Saving as an Idea (instead of scheduling immediately) gives you a staging area to add your take and pick the platform later, which is the whole point of curating in batches. You can also highlight a key sentence on the page, right-click, choose Buffer, and Save Idea to capture the quote you want to build around.
Write a take, not a link-dump. This is the step that decides whether the post earns a click. Open the Idea and replace the auto-pulled headline with your angle: the one sentence on why this matters, the surprising stat, the line you disagreed with, or how it changes what your audience should do. A share that says "interesting read 👇" is invisible; a share that says "This report is why I stopped [doing X] — here is the number that convinced me" gets read. The article is your raw material; your commentary is the post.
Use Buffer's AI Assistant to draft per-platform variants. In the composer, Buffer's AI Assistant drafts a post from a prompt of four words or more (paste your notes on the article), and once you click Customize for each network it can rephrase, shorten, or expand each channel's version: a longer LinkedIn take, a punchier X post, a Threads variant. Use it to draft, then rewrite the opening line in your own voice: the AI summary tends to read like the source article, and the whole reason to add commentary is to sound like you, not the publisher. Tailor each variant to its platform's ceiling and norms rather than posting one caption everywhere.
Attribute the source and place the link correctly. Credit the author or publication — it is both honest and it is what makes people trust your recommendation. Then decide where the link goes. Plenty of creators put the take in the post and the link in the first comment or reply, on the theory that link posts get less reach. Platforms don't publish that rule, so test both placements on your own account. Keep quoted text to a short snippet, not a wholesale paste of the article.
Convert the Idea to a scheduled post and queue at your cadence. When an Idea is ready, schedule it as a draft or a post, select the channels, and add it to your Buffer queue rather than blasting the whole batch at once. Space the saved-article posts across your posting schedule so they sit alongside your original content, not in a wall of links. Run this loop weekly — a short triage-and-queue session clears the backlog steadily and keeps a reliable share of your calendar filled without new writing.

What makes shared-article posts fall flat?

Sharing the link with no commentary. "Great read 👇" gets scrolled past. The post is your angle on the article — why it matters, what surprised you, what to do about it — not the headline Buffer auto-pulled.
Posting an article you only skimmed. Saved is not read. Share something you skimmed and you will eventually recommend a piece that argues the opposite of what you assumed; read before you queue.
Never testing link placement. Many creators believe in-body links cost reach and move the link to the first comment or reply. Try both on your own account before you settle on one.
Letting the Ideas board become a graveyard. Saving to Buffer without a weekly convert-and-queue session just moves the backlog from one app to another. The cadence is the workflow, not the capture.
One caption for every platform. A LinkedIn take, an X post, and a Threads note read differently. Use the AI Assistant to draft per-platform variants and truncate to each ceiling at a word boundary.
Sharing stale saves. Timely articles die fast — a saved "this week" piece is worthless a month later. Triage for freshness and drop anything the moment has passed.
Over-quoting or lifting the article's images. Attribute the author, keep quotes to a short snippet, and do not reuse the publisher's photos as your own — link out instead.

Legal note

Sharing a link and a short quote with attribution is normal commentary, but the article itself is copyrighted. Do not paste the full text of a piece into your post, do not reproduce the publisher's images as if they were yours, and keep any quotation to a brief, clearly-attributed snippet that supports your own commentary. Naming the author and publication is both the ethical and the practical move — it credits the source and it makes your recommendation more credible. When you are drafting with an AI assistant, the same rule applies to its output: a machine summary that closely paraphrases the whole article is still riding on someone else's work, so add your own analysis rather than republishing theirs.

Where does Kompozy fit if one link per article is not enough?

Buffer's extension is genuinely good at what it does: one click sends a saved article to your queue, and the AI Assistant will summarize it. But look at what that leaves you with — one text caption, linking out to someone else's page, in whatever voice the summarizer defaulted to. Kompozy treats the same saved article as a source that feeds a full generation engine, not a link to forward. Drop the article in — paste the URL or text, or wire your read-it-later export in as a webhook input — and instead of one caption you get a spread built from that one read: a Text Post with your take, a Carousel that breaks the article's argument into slides, a Quote Graphic of its sharpest line, a Persona Short where your avatar explains why the piece matters on camera, and a Blog Article that expands your commentary into a page you own and link from — any of 20 output formats off one saved article, so a reading habit becomes a week of original content instead of a single referral out.

The two things this guide tells you to add by hand are the two things Kompozy does automatically. The voice: every output is governed by one Persona Brief plus banned-word filters, so the caption never reads like the publisher's summary — it reads like you, which is the whole point of sharing with a take. The cadence and the guardrails: Autopilot schedules the batch across up to nine social platforms plus blog and email from one queue, handling per-platform limits and where the link should sit, and every draft passes a per-post review gate — the checkpoint where you confirm attribution and keep quotes to a snippet rather than republishing the article. Honest framing: if all you want is to save a link and get it out fast, Buffer's extension is the lighter tool and this guide is the whole workflow. Kompozy is for the creator who wants the backlog to become a content engine — one saved article generating an on-brand spread across every channel, not one more link in the feed. Starter ($199/mo for 5,500 credits, 4 platforms) fits a solo creator turning a weekly reading pile into posts; Pro ($499/mo for 18,000 credits, 9 platforms) runs it across several brands or higher volume with autopilot; Enterprise is available through Contact Sales for agencies curating for many clients at once.

What does this look like in Kompozy?

A real quote graphic generated in the Kompozy workspace, shown as an example of the format. It was not made for this guide or for any customer.

Quote graphic generated in Kompozy — Real output · Kompozy Quote graphic format · from the Kompozy workspace

Who is this for, and who should skip it?

Best for:

Creators with a backlog of saved articles and a clear point of view.
Buffer users who want a weekly curation routine.
Accounts that mix curated links with original posts.

Not ideal for:

Anyone who shares links without reading them first.
People expecting Buffer to pull from Instapaper or Readwise automatically. It doesn't.
Accounts that would turn into a wall of links with no commentary.

Frequently asked questions

How do I save an article to Buffer from my browser?

Install the free Buffer browser extension (Chrome, Safari, Opera, or Edge), open the article, click the Buffer icon, and choose "Save Idea" to park it on your Ideas board or "Create Post" to go straight to the composer. You can also highlight a sentence, right-click, select Buffer, and save the quote you want to build a post around.

Does Buffer connect to Pocket or my read-it-later app?

No — Buffer has no direct read-it-later integration, and Pocket itself shut down in 2025. The bridge is Buffer's browser extension: open a saved article from wherever your list lives now (Instapaper, Readwise Reader, Raindrop, a browser reading list, or bookmarks) and send that page to Buffer with the extension.

Should I save an article as an Idea or create a post right away?

Save it as an Idea when you are triaging a batch. The Ideas board is a staging area where the link, title, and image are captured as a draft, so you can add your take and pick the platform later, then schedule it as a draft or a post when it is ready. Create Post is for the rare case where the caption is already in your head.

Can Buffer's AI write the post from the article for me?

Partly. Buffer's AI Assistant writes a draft from a prompt and can rephrase, shorten, or expand it for each channel in the composer. Treat that as a first draft: rewrite the opening line in your own voice and add your angle, because an AI summary reads like the source and the reason to share is to add something the article did not say.

Where should I put the article link so my reach is not penalized?

There is no single right answer. Many creators put the commentary in the post and the link in the first comment or reply because they believe link posts get less reach, but platforms don't publish that rule. Test both placements on your own account and keep whichever does better.

How many saved articles should I actually share?

Far fewer than you saved. Keep only the pieces on your lane that are still timely and that you can add a real angle to, and space them across your queue alongside original content. A weekly triage session that clears the few worth sharing beats dumping the whole backlog in one wall of links.

How do we know this?

On 2026-10-23 we checked the Buffer extension, Ideas and AI Assistant features against Buffer's help center, and the Pocket shutdown dates against Mozilla's announcement. Claims about link reach that platforms do not publish were removed. Kompozy plan details come from kompozy.io/pricing. Figures we could not confirm were removed or reworded.

Sources

Buffer Help: Buffer browser extension (read 2026-10-23)
Buffer Help: Creating ideas in Buffer (read 2026-10-23)
Buffer Help: Using Buffer's AI Assistant (read 2026-10-23)
Mozilla: Building what's next (Pocket shutdown) (read 2026-10-23)
Kompozy: Pricing (read 2026-10-23)