# How to turn a newsletter archive into a book

Export your archive, then treat it as raw material: pick one theme, drop the issues tied to their week, and group what’s left into chapters with new writing between them. Exports come in different forms (a zip from Substack, a CSV from beehiiv, JSON from Ghost), so plan on moving the chosen issues into a document or working from their web pages.

Last reviewed 30 October 2026. Web page: https://chapbook.ink/guides/turn-newsletter-archive-into-a-book/

## Get the archive out

Every platform does this differently. These are the steps as each platform’s help pages gave them when we checked on 30 October 2026.

| Platform | Where to find it | What you get |
|---|---|---|
| Substack | Settings, Exports, “Create new export” | A zip file of your publication’s data, including posts |
| beehiiv | Settings, Export Data, Export Posts, “Export All Posts” | A CSV of all posts, including archived and draft ones, by an email link valid for 24 hours |
| Ghost | Settings, Advanced, Import/Export, Export tab, “All data” | A zip with your posts in JSON and a CSV of per-post sends, opens and clicks |

On another platform, look in its help pages for an export of posts or campaigns. If there isn’t one, your public archive page still lists what you have sent, and you can work from that.

Check who owns the words, too. Substack’s terms say “you own what you create”, and Ghost describes “full ownership of your content and data”. On another platform, read its terms. Pieces by guest writers are a separate matter, so ask them before you include them.

## Why an archive isn’t a book yet

A newsletter is written for one week. It assumes the reader saw last week’s issue, cares about this week’s news, and will be back next week. A book has none of that. Its reader arrives once, knows none of your running jokes, and has to get everything from the page.

So the issues that made your newsletter feel alive are often the first to go: the news reaction, the link roundup, the reply to a reader’s email. What survives is the part that would still be true for someone who found it in three years.

## Choose a shape

- **A book on one theme.** Chapters built around an argument, with issues merged and rewritten to serve it. This is the most work and usually the most useful to a stranger.
- **A selection with notes.** Your best pieces largely as written, each with a short new note on why it’s there and what you think now. It’s quicker and suits a writer whose voice is the attraction.
- **A chronicle.** Issues in date order, when the passing of time is the story: a year building a company, or a season of a project. It’s rarer, and it only works if something changes along the way.

Whatever the shape, use your numbers as a clue, not a verdict. An issue with a high open rate may have had a good subject line and nothing lasting in it. Ghost’s export includes per-post opens and clicks, and a spreadsheet of your issues with a keep, rewrite or drop column is often all the planning tool you need.

## If some issues were paid

Paying subscribers bought access to those issues, so tell them before they see the book on sale. Giving them an early or free copy is a simple way to thank them. If paid issues are going into the book, say what’s new in it, so that nobody feels sold the same thing twice.

If you plan to enroll the ebook in KDP Select, read its terms first: the ebook “must also be exclusive to the Kindle Store” during the 90-day enrollment, and it “can only be distributed through KDP and public libraries.” KDP’s pages don’t mention newsletters or web archives, so ask KDP if the same text stays online.

## Where Chapbook fits

Chapbook’s [“I have a draft”](/manual/start-a-book/#start-from-your-own-draft) doesn’t read a platform’s export file directly. It takes Word, Markdown or plain-text files, up to 10 at a time, or up to 20 links, each of which becomes a chapter word for word, as text only. Links are read without signing in, so use public pages: a paywalled issue gives only what a stranger would see. Put selected issues into a document, or paste the links of the ones you kept, then merge, split and leave out chapters before the book is created. Importing is free, and any AI action on the book afterwards costs credits.

Choose the kind that matches the result: a nonfiction book for a themed book, or a lead magnet for a short selection to welcome new subscribers. On a paid plan, a book can have its own page where readers sign up. The sample on this page is not an imported archive. It is a guide on newsletter welcome sequences, generated from one brief, and it shows what a short book for a newsletter’s readers looks like when it’s typeset.

## What to do

1. **Export everything first.** Get a full copy before you decide anything. It is your backup and your working list, and reading the titles in one place shows you what you have actually been writing about.
2. **Find the book’s one theme.** Look for what you keep coming back to. If one subject runs through many issues, that’s the book. Say in a sentence what a new reader will get from it.
3. **Sort issues into keep, rewrite and drop.** Keep what still holds up, rewrite what has a good idea in a dated wrapper, and drop link roundups, news reactions and announcements. Most archives shrink a lot at this step.
4. **Group the keepers into chapters.** A chapter may be several issues merged, not one issue each. Order the chapters as a new reader needs them, not by the dates you sent them.
5. **Strip the email out of it.** Remove greetings, sponsor messages, referral asks, shout-outs and “see you next week”. Keep the voice, which is what your readers came for.
6. **Offer it to your subscribers first.** They read these issues before anyone else, and some may have paid for them. Tell them what the book is and what is new in it before you announce it elsewhere.

## Made with Chapbook: The Welcome Sequence

The Welcome Sequence: Seven emails that turn a subscriber into a reader, by Dana Okafor. Lead magnet, 3,626 words, 17 pages. A sample generated from one brief and exported unedited; it is not a customer's book. Read every page: https://chapbook.ink/examples/newsletter/

The brief:

> A seven-email welcome sequence for a new newsletter: what each email does, what to write, and when to send it. Promise: By the end you have a complete seven-email welcome sequence drafted, with a send schedule. Reader: Someone with fewer than a thousand subscribers who writes the newsletter themselves. Voice: Second person, warm and direct, worked examples with fictional newsletters, no invented open-rate statistics.

The outline the planner proposed:

1. Introduction (282 words)
2. Email 1: The one they actually open (681 words)
3. Emails 2 and 3: Who you are and what to expect (729 words)
4. Emails 4 and 5: Your best two pieces, reframed (669 words)
5. Emails 6 and 7: The ask, and the door left open (743 words)
6. The schedule and the template (478 words)

## Questions

### Can I export my newsletter archive from Substack?

Yes. Substack’s help center says to open Settings, choose Exports and create a new export, which produces a zip file of your publication’s data, including posts, as of 30 October 2026.

### Can I export my posts from beehiiv?

Yes. Under Settings, Export Data, choose Export All Posts for a CSV. beehiiv says it covers published, archived and draft posts, and its download link lasts 24 hours, as of 30 October 2026.

### Do I own my Substack posts?

Substack’s Terms of Use, last updated 6 October 2026, say “you own what you create” and that original content you post “remains yours”. Guest pieces may belong to their authors.

### How many issues do I need for a book?

There is no set number. Group by theme and count the words that survive the cut. A few strong issues can make a short guide, and years of them may make only one real book.

### Should I use Chapbook’s Newsletter kind for an archive?

No. In Chapbook, Newsletter means one designed issue of up to 4,000 words. An archive suits a nonfiction book, or a lead magnet if you are making a short selection.

## Sources

- [Substack Help Center, “How do I export my posts?”](https://support.substack.com/hc/en-us/articles/360037466012-How-do-I-export-my-posts)
- [Substack, “Terms of Use” (last updated 6 October 2026)](https://substack.com/tos)
- [beehiiv Knowledge Base, “Exporting post content or subscriber data from beehiiv” (updated 28 October 2026)](https://www.beehiiv.com/support/article/12258595483543-exporting-post-content-or-subscriber-data-from-beehiiv)
- [Ghost, “Exporting content and data”](https://ghost.org/help/exports/)
- [Amazon KDP, KDP Select enrollment requirements](https://kdp.amazon.com/en_US/help/topic/GD9PMU58BV24QFZ7)