Initializing... drag & drop files here
Supports: PUB
Converting a .pub to MOV does not produce a "video of your document" in any cinematic sense — it produces a slideshow. Each page of the Microsoft Publisher file is rendered to an image and those images become the frames of a QuickTime movie, held on screen for a set number of seconds each. That is genuinely useful for putting a brochure on a lobby display, dropping a newsletter into a Final Cut or iMovie timeline, or posting a flyer somewhere that accepts video but not documents. This page covers what the pipeline actually does, which codec choices are safe, and the two ways the conversion can go wrong.
| Property | Value |
|---|---|
| Container | QuickTime File Format (.mov), Apple, introduced 1991 |
| Default video codec | H.264 |
| Audio | None — the output is silent, and the audio controls do not render |
| Frame rate | 1 fps (fixed for still-image sources) |
| Frames | One per page of the publication |
| Default time per page | 5 seconds |
| B-frames | Disabled for still content |
| Maximum frame size | Pages are normalised to at most 4096 px on the long edge |
| Rate control offered | Quality Preset, Constant Quality, Constraint Quality |
.pub onto the page or click "+ Add Files" to browse. Multiple files can be queued, and "Merge strategy" controls whether they combine into one movie or produce one movie each..mov — see the compatibility table below. H.264 is preselected and is the right answer in almost every case.The codec dropdown is shared across video targets, so it offers far more than QuickTime meaningfully supports. The important thing to understand is that picking an unsuitable codec usually does not produce an error — the file is written anyway, with a non-standard identifier that Apple software cannot decode.
| Codec | Safe in a .mov? | What actually happens |
|---|---|---|
| H.264 (default) | Yes | Written as a standard avc1 track; plays everywhere |
| H.265 / HEVC | Yes | Written as a standard HEVC track; needs a reasonably modern player |
| MPEG-4 | Yes | Written as a standard mp4v track |
| MJPEG | Yes | Large files, but a valid and edit-friendly QuickTime track |
| H.261, H.263, H.263+ | Avoid | Also snap the frame to a small fixed size, ignoring your resolution choice |
| MPEG-1 | Fails | Rejected outright on a still-image source |
| Everything else in the list | Avoid | Muxes without an error, but the track is tagged outside QuickTime's standard set |
Because there is no audio anywhere in the chain. A .pub is a page-layout document with no sound track, so the pipeline explicitly encodes a video-only file and hides the audio codec controls — there is no setting to change. If you want narration or music over the slideshow, import the finished .mov into a video editor and add the audio there.
Multiply the number of pages by the time per page. With the 5-second default, a four-page newsletter produces a 20-second movie. "Image Duration" adjusts that from a fraction of a second up to 10 seconds per page, so the same four pages can be anything from a near-instant flash to 40 seconds. There is no way to give individual pages different durations in a single pass.
H.264 is the safe default and imports everywhere. If you want something friendlier to frame-accurate scrubbing, MJPEG stores every frame independently, which editors handle very comfortably — at the cost of a much larger file. Avoid the long-tail codecs in the dropdown entirely: in our testing, options such as Theora, WMV and HuffYUV were written into the .mov with non-standard identifiers (theo, WMV2, HFYU) rather than being rejected, so the conversion appears to succeed and then the file will not open in Apple software.
MP4 unless you have a specific reason not to. The two containers are closely related — MP4's structure derives from QuickTime — and both carry H.264 equally well, but MP4 is the more universally accepted target for web upload, messaging and Windows playback. Choose MOV when you are working inside Apple's ecosystem or handing the file to Final Cut or iMovie. Compare with Publisher to MP4.
A slideshow of static pages has no motion to sample, so encoding at 1 fps is the efficient choice — a higher rate would just duplicate identical frames and inflate the file. Players handle it fine; the pages simply hold on screen. It does have one consequence worth knowing: codecs that require a standard broadcast frame rate, MPEG-1 in particular, cannot be used at all on this path.
Only the padding bars. Publisher pages are rendered onto an opaque white background before encoding, so there is no transparency left to fill. The colour therefore shows up when you choose a resolution whose shape differs from the page — a tall A4 page placed in a 1920 × 1080 frame leaves pillarbox bars either side, and that is what gets coloured.
Not on this path. Still-image sources only expose Quality Preset, Constant Quality and Constraint Quality — the bitrate and target-file-size modes are hidden because a still image has no source bitrate to scale from. Quality Preset, which starts at "Very High (Recommended)", is the control to reach for first; Constraint Quality lets you set a ceiling on the maximum bitrate. Failing that, lowering the resolution is the most reliable way to shrink the output.
No. Every page becomes a raster frame, so all the text is pixels — it cannot be searched, selected or copied from the video. If keeping the words intact matters, convert to Publisher to PDF instead, or produce page images with Publisher to JPG alongside the video.
Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public. For long publications the practical limit is upload time rather than the page count.