Korva vs Microsoft Publisher: The Replacement

Korva is the closest thing to a direct Microsoft Publisher replacement, because it does the two things a replacement actually has to do: open your existing .pub files, and feel enough like Publisher that you aren't relearning a career. It is not a clone, though. Publisher has a handful of features Korva simply doesn't reproduce, and the imported layout will need a tidy. Here's the honest feature-by-feature comparison.

Microsoft retires Publisher on October 1, 2026. There is no Publisher 2027 and no successor product. That leaves a very specific gap, and the tools rushing to fill it mostly solve half the problem: some are lovely design apps that cannot read a .pub file, others read the file but hand you something you’d rather rebuild. This article is the direct head-to-head — Korva against Publisher itself, feature by feature, including the parts where Publisher wins.

Two neighbouring articles, so you land in the right place. If you want the wider field of options — Affinity, Canva, Scribus, LibreOffice, Microsoft 365 — read our roundup of Microsoft Publisher alternatives. If you’ve already decided and want the project plan, our step-by-step guide to replacing Microsoft Publisher walks through inventory, batch export, template rebuilds and training. This page is narrower: what you gain, what you lose, and what your muscle memory maps to.

One note up front. Microsoft, Microsoft Publisher and Microsoft Word are trademarks of Microsoft Corporation; Avery is a trademark of its owner. Korva is an independent product, not affiliated with, authorised by, or endorsed by Microsoft.

The one question that decides it

Before any feature list, ask yourself one thing: how much of Publisher did you actually use?

Not how much of it existed. How much you touched. Almost everybody who asks this question discovers the same thing. They used text boxes, pictures, a template or two, page setup, and Export to PDF. Maybe mail merge for labels or certificates. Maybe a master page for a page number. That’s it — perhaps fifteen percent of the ribbon, used every week for a decade.

The other eighty-five percent is where Publisher’s genuine, unreplicated features live: Building Blocks, design sets, colour schemes and font schemes, WordArt, commercial-print colour separations, publish-to-web. If those are load-bearing for you, no replacement on the market — including Korva — is going to feel complete, and you should know that before you download anything.

So hold your own answer in mind as we go. The comparison below is roughly ordered by how likely you are to care.

What actually happens on October 1, 2026

Let’s clear this up, because the rumours are worse than the reality.

Your files do not stop working. A .pub file is a container of bytes on your disk. Nothing about a support date reaches in and changes it. On October 2 the file is byte-identical to what it was on September 30.

What ends is the software’s support life. Publisher leaves Microsoft 365 — subscription installs stop getting it — and it stops receiving fixes, including security fixes. Microsoft’s own guidance is to convert your documents to PDF for viewing and to Word for editing, which is a slightly strange instruction given that Word has no .pub import filter at all. There is no conversion path inside that advice; there’s a suggestion to already have converted.

If you own a perpetual copy that’s already installed, it will keep launching. Be clear-eyed about what that is, though: an unsupported binary with no security fixes, on a machine that will eventually be replaced or updated out from under it. That’s a countdown, not a plan. Use the time to export PDFs while the app that renders them best still runs. Our breakdown of Publisher’s end of life in 2026 covers the timeline in more depth, and what happens to .pub files covers the file-format side.

The practical risk isn’t the date. It’s the lock-in. A proprietary format whose only fluent reader is being retired is the actual problem, and it’s the problem a replacement has to solve first.

Opening .pub: the part that decides everything

This is where most Publisher replacements quietly fail, so let’s be precise about what Korva does and doesn’t do.

The .pub format is a proprietary CFB/OLE2 compound binary, and its page-geometry stream — the part that says exactly where each box sits — is undocumented. That single fact explains the entire landscape. It is why Word has no import filter, why Scribus’s experimental importer is fragile, why LibreOffice Draw is hit-or-miss, and why nothing on earth reproduces a Publisher layout perfectly. Anyone promising pixel-identical conversion is overselling.

Korva’s approach is deliberately modest and it works. It extracts the text, with accented characters preserved, and every embedded image, then places them on a clean editable page. This is “open and fix”, not a pixel-perfect clone. You get your content back, nudge boxes into place with the snapping guides, and move on. For a template you reprint weekly, that’s ten to twenty minutes paid once.

Two details in that screenshot matter more than they look. First, the accents survive — a lot of converters mangle non-ASCII text, and if your documents are French, Spanish or German that’s the difference between usable and useless. Second, the import health panel: your original .pub is never modified. Opening produces an editable copy. If the import disappoints you, nothing has been lost and you can try again with a different approach.

Korva’s own save format is a versioned zip-based package that uses the familiar .pub extension, and opening sniffs the content — Zip versus OLE2 — so a Korva-saved file and a genuine legacy Publisher file both open correctly. You don’t have to think about which is which.

If you need one safe PDF, use the free browser converter or finish one complete project in the desktop app. A larger archive is what Pro’s batch action is for.

Where your Publisher muscle memory lands

The second job of a replacement is not making you feel stupid on day one. Korva’s editor is a ribbon-style UI built deliberately for people arriving from Publisher: Home, Insert, Page Design and Mailings tabs, with Clipboard, Font, Paragraph, Objects, Styles, Arrange and Editing groups underneath. There’s a Format task pane on the right and a page-thumbnail panel on the left, which is more or less where your hands already expect them.

The interactions map across too: drag to move with smart snapping guides, eight resize handles, double-click for in-place text editing, picture pan, zoom and flip, multi-select with align and distribute, rotation, a layers and objects panel, find and replace, 100-step undo, live page thumbnails, zoom, shapes and tables. There’s also a built-in “Coming from Microsoft Publisher?” tour that maps the ribbon, task panes and shortcuts explicitly, for the handful of things that did move.

Page setup will feel familiar as well: presets for Letter, Legal, Tabloid, A3, A4, A5, B5, postcard, business card, banner and a number 10 envelope, plus custom sizes and orientation switching. Templates cover bulletins, flyers, business cards, certificates, Avery 5160-compatible address labels, newsletters, brochures, postcards, greeting cards, programs, gift certificates, menus, posters, invitations, resumes, event tickets, letterheads and blanks. If your weekly job is the church bulletin, we walk through it end to end in how to make a church bulletin.

What Korva does that Publisher never did

A replacement that only matches the original is a downgrade, because you paid switching costs for nothing. Three things here are genuine gains.

It runs on your Mac and your Linux box. Publisher was Windows-only for its entire life. Every Mac user who ever received a .pub attachment knows the feeling. Korva is a desktop app for Windows, macOS and 64-bit Linux, and the same files open on all three, so a mixed team — office PC, someone’s MacBook, a volunteer’s Linux laptop — finally works from identical documents. If you’ve been searching for Microsoft Publisher for Mac, this is the actual answer to that question. There’s no mobile app, to be clear; Korva is desktop only.

It’s genuinely offline, and it’s one payment. No account, no sign-in, no telemetry; files never leave the machine. That matters for member directories, donor lists and student records in a way that rules out browser-based converters entirely. Korva Pro is a one-time US$49 for one movable computer — activate online once, then work offline indefinitely. No subscription, and no repeat of the Microsoft 365 experience where the app you depend on can be withdrawn from under you.

Its print handoff has grown past where Publisher stopped. As of v1.7.0, PDF export supports composite CMYK (DeviceCMYK), printer’s crop and trim marks with a quarter-inch bleed margin, /TrimBox and /BleedBox tagging, registration marks with a CMYK calibration bar, and grayscale export, behind three presets: “Screen & email”, “My own printer” and “Print shop”. Photos embed losslessly — JPEGs go in via /DCTDecode rather than being re-compressed. And Pack and Go is here, deliberately named after Publisher’s own: one Zip for the print shop containing the editable document, a press-ready PDF with crop marks, every picture at full resolution, and a README naming which fonts embed and which get substituted. That last file saves a phone call.

Autoflow deserves a mention too. When a story overflows its box, it runs on into fresh boxes on new pages and generates “Continued on page N” and “Continued from page N” notices automatically, with linked text chains resolving across the whole document. Mail merge reads a CSV with {{field}} placeholders to produce one filled page per record, plus Avery label sheets and catalog/directory merges.

What you’ll miss from Publisher

Now the honest half, stated without hedging, because you’ll find these out anyway and I’d rather it were here.

Building Blocks and design-set galleries are gone. Publisher’s pre-built page parts — the borders, accent bars, calendars, advertisement blocks, the coordinated design sets — have no equivalent in Korva. If you built pages by dropping in Building Blocks, your workflow changes shape. You’ll be composing from shapes, text boxes and templates instead.

Colour schemes and font schemes are gone. Publisher’s ability to recolour an entire document by picking a named scheme was genuinely good, and Korva has nothing like it. Consistency is on you, or on a master page.

WordArt is gone. No stretched, arced, shadowed display text. Some readers will regard this as an improvement. Others have a certificate that depends on it, and for those, this is a real loss.

Publish-to-web is gone. Publisher’s HTML export isn’t reproduced.

Commercial-print colour separations are not there. Composite CMYK, yes. Separations, spot colours, ICC colour management and profiles, PDF/X conformance — no. If your printer’s spec sheet lists any of those words as a hard requirement, Korva is the wrong tool for that specific job and Scribus is where you should look instead. Note that Publisher itself was thin here too, but it wasn’t nothing.

And the layout won’t come back pixel-identical. I’ve said it twice already and I’ll say it a third time, because it’s the single most common disappointment: an imported .pub gives you your content on a clean page, not a mirror of the original. Budget the tidy-up.

Korva vs Microsoft Publisher: the comparison table

Your migration checklist

Four steps, in this order. The detail lives in our full replacement guide, but this is the shape of it.

1. Inventory your .pub files. Search every machine, shared drive and USB stick for *.pub. Sort them into live documents you re-edit, templates disguised as documents, and archive you only read. The live list is almost always shorter than you fear.
2. Convert the archive to PDF for safekeeping. Do this while something that reads .pub well is still running. For everything in the archive bucket, the PDF is the migration — once it exists, that file is finished.
3. Rebuild the two or three templates you actually reuse. Open each one, let the import bring back the text and images, spend fifteen minutes tidying, then save it as your new clean master. You do this once per template, ever.
4. Keep the originals. Don’t delete a single .pub. Storage is cheap, and a better importer might exist in two years. Korva never modifies them anyway — it opens an editable copy — so keeping them costs you nothing but disk space.

The bottom line

Publisher is not being replaced by Microsoft. It’s being retired into a gap, and the honest question is which tool covers the part of that gap you personally stand in.

If you used Publisher the way most people did — a bulletin, a flyer, a certificate, some labels, Export to PDF — Korva covers it, on whatever computer you own, offline, for a single US$49 payment, and it will open the old files nobody else will touch. If you leaned on Building Blocks, colour schemes and WordArt, or you send separated CMYK to an offset press, you’ll feel the absences and you deserved to hear that before downloading anything.

The cheapest way to settle it is your own file. Download Korva, finish and export one complete project — no account, nothing uploaded, original untouched — before deciding anything else.