Will My Publisher File Look the Same After Converting?

If you've got years of newsletters, bulletins, or flyers sitting in Publisher, the question that actually matters isn't “can this be converted” — it's will it still look like my file when it's done? That's a fair thing to worry about. A lot of file converters technically “work” but quietly rearrange your layout, drop a photo, or swap out your fonts for something generic. Here's an honest, specific answer — not a marketing promise, an actual walkthrough of what happens to each part of your document.

The short answer

We don't run your .pub file through a program that guesses at Publisher's file format. We open it in the real Microsoft Publisher application — the same program you'd use yourself — and let Publisher do the exporting. That's the reason the output tends to come out looking like your file: nothing is reverse-engineering or reinterpreting your layout, because the software that actually understands Publisher files is the one doing the work.

That doesn't mean nothing can ever go wrong — no conversion process for a 20-year-old file format can honestly promise that, and we won't tell you otherwise. But it does mean the starting point is as faithful as it can be, and below we'll walk through exactly what that gets you, element by element, plus the few things worth knowing about.

Photos and pictures

We check for pasted-in photos two different ways — once by reading the file itself, and separately by scanning the images inside the PDF that Publisher generates — then combine what each method finds. We do it twice because either method alone occasionally misses an image the other one catches. Once we've found a picture, it gets packed directly into your new file rather than just linked to it, so pictures we find travel with the document rather than needing to be located again.

Images linked from your computer, not pasted in

If a picture in your document is linked to a file on your computer rather than pasted directly in, we first look for it in its original location. If it's been moved, renamed, or reorganized since you built the file, we still try to track it down — matching it against the pictures we've already found by filename, and if that doesn't work, by its size and shape. Only if an image genuinely can't be located anywhere does it come through as a blank placeholder instead of a guess. The one real gap: if you have several very similarly sized, similarly shaped photos in one document, this size-and-shape matching could occasionally attach the wrong one to the wrong spot — a narrow edge case, but an honest one worth knowing about. (The much more common case — cloud-only images in OneDrive or SharePoint that haven't been synced to your computer — simply won't be found at all; sync them locally first and they'll come through normally.)

GIFs

Two separate things had to be handled here. First, the programs that open your converted file (Affinity, InDesign) can't actually display a GIF directly, so we automatically convert any GIF to a standard image format behind the scenes — you'll see the picture, not a broken-image icon. Second, GIFs that are buried inside a grouped set of objects (say, a GIF grouped with a caption and a border) used to be missed by a straightforward export, so we built a more thorough fallback specifically to catch those. Both issues are resolved and this is now reliable.

Text, text boxes, and fonts

Text formatting is read character by character, not just paragraph by paragraph — so if you bold one word in the middle of a sentence, italicize a phrase, or switch fonts partway through a line, that carries over instead of flattening to one style for the whole paragraph. Font names carry over accurately. What doesn't travel is the font file itself — if you used an uncommon font and the computer opening your converted file doesn't have it installed, that program will substitute a different font, the same way any program does when you open a file that references a font you don't have. That's not something we can work around; it's just worth knowing so text doesn't look “wrong” and you think something broke.

Content sitting outside the page (the “scratch area”)

This is one of the more genuinely distinctive things about how we do this. If you just export a Publisher file straight to PDF yourself, anything sitting outside the printed page — reference photos, draft text, notes you parked off to the side while working — gets silently left behind, because a PDF only captures what's printed. We specifically look for anything sitting outside the page boundary and bring it along into your converted file too, instead of quietly dropping it the way a plain export would.

Grouped objects and layered layouts

If you've grouped a photo with its caption, or a shape with a border around it, a lot of naive converters flatten that whole group down into a single flat picture — which means you can no longer move, edit, or resize any individual piece of it once it's converted. Ours keeps each piece of a group as its own separate object, in the same position relative to the others, so a grouped photo-and-caption still comes through as an editable photo and an editable caption — not one flattened image standing in for both.

A few things worth knowing

Being upfront about limitations is part of being honest about accuracy — a service that claims to handle everything perfectly, every time, isn't one you should trust with 15 years of bulletins. A few real caveats:

• Password-protected files — Publisher can't open a password-protected file through automation any more than you could without the password. Remove the password before uploading.
• Images stored only in the cloud — if a linked image lives in OneDrive or SharePoint and isn't synced to a local folder, it won't be there to pull in. Sync it locally first and it'll come through fine.
• Missing fonts — font names carry over, but the font files themselves don't travel with the conversion. If a font used in your document isn't installed on the computer opening the result, Affinity or InDesign will substitute something else — the same way any program does when a font isn't available.
• Photos occasionally get stretched to fit their frame — when a photo's proportions don't exactly match the frame it sits in, the photo is scaled to fill that frame rather than cropped, which can very occasionally stretch it slightly. Easy to fix by adjusting the fit once it's open, but worth knowing rather than assuming every image lands pixel-perfect.
• Very old file versions — we support what Publisher 2019/Microsoft 365 can open, which covers Publisher 2003 through current. Genuinely ancient Publisher 2.0/95 files may not be supported.

None of this is unique to us — it's the honest reality of any conversion process working with a file format this old. The difference is we tell you upfront instead of finding out the hard way after you've paid.

What happens if something doesn't come through right

Every file is different, and every so often, one won't convert cleanly. Here's exactly what happens, no fine print:

• Any file we can't convert is refunded automatically within 24 hours of processing starting. You're only ever charged for files that actually convert.
• If something goes wrong with the whole job — rare, and typically only happens if Publisher itself becomes unavailable on our end — you get a full refund, also issued automatically within 24 hours of processing starting.
• Refunds land back on your card within 5–10 business days, depending on your card issuer.

That's not a footnote we're hoping you skip past — it's the honest other half of an accuracy claim. We're confident in what comes through intact because of how the conversion actually works — real Publisher doing the exporting, not a guess — but “confident” isn't the same as “guaranteed,” and we'd rather build in a safety net than pretend one isn't needed.

The bottom line

Because your file is opened and exported by the real Microsoft Publisher application, what comes out is as close to what you'd get exporting it yourself as a conversion process can be — your photos, your text boxes, your fonts, even content sitting off the edge of the page. It's not flawless, and we're not going to tell you it is. But it's specific, it's honest, and if a file can't be converted, you're not out the money for it.