Why Word, Excel and PowerPoint exports can change layout

Office conversion is a layout calculation, not a screenshot of the editing window. Fonts, page settings and application-specific features can change the result, so inspect the exported PDF against the source’s intended print view.

The source application contains more than visible text

A Word file can contain sections, styles, anchored images, fields and pagination rules. A spreadsheet contains cell values, formulas, print areas and page breaks. A presentation contains slide objects, themes, notes and sometimes animation or media. Turning these structures into fixed PDF pages requires decisions about how they should be rendered.

SandboxPDF uses a local LibreOffice engine for supported Office imports. The document is processed on your device rather than sent to a conversion service. That privacy property does not imply perfect equivalence with every version of Microsoft Office or every file feature. Different layout engines can make different choices while reading the same source.

Start by identifying the intended deliverable. A spreadsheet’s entire workbook and its configured print area may be very different things. A presentation’s speaker notes may not belong in the slide PDF. A Word document’s tracked changes may need to be resolved before distribution. Conversion cannot decide those editorial questions for you.

Fonts can move more than a few letters

When a font is unavailable or substituted, character widths and line heights may change. A paragraph can gain an extra line. A table row can become taller. A heading can move to the next page, carrying following content with it. The visible difference may begin with one font and propagate through a long document.

Check the source’s fonts and any licensing or embedding constraints. If you control the document, choose fonts appropriate to the intended conversion environment. Do not assume that a familiar font name guarantees identical metrics on every device. Special symbols and non-Latin scripts deserve explicit inspection in the exported PDF.

Review the last lines of pages, table boundaries and places where figures are anchored. Those are common locations for pagination changes. Compare the number of pages, but remember that matching counts do not prove matching content. Two pages can have different breaks while the total remains the same.

Word: sections and anchored objects matter

Word documents may contain different page sizes, orientations, headers and footers in separate sections. An explicit page break is different from an empty paragraph used to push content down. A floating image can be anchored to a paragraph while appearing elsewhere on the page. These relationships can behave differently during conversion.

Before exporting, remove unnecessary layout hacks where possible. Use deliberate page and section settings in the source. Check whether tables can split across pages and whether headings stay with the following paragraph. If the document contains a table of contents or page-reference fields, update them in the source application when appropriate.

After conversion, inspect headers, footers, page numbers and the placement of images relative to their captions. Check the final page for overflow or a new blank page. A PDF can look generally polished while a caption has become separated from the figure it explains.

Excel: printing is not the same as viewing cells

A worksheet can extend far beyond a physical sheet of paper. Its PDF output depends on print areas, scaling, orientation, margins and page breaks. A few formatted cells far from the main table can sometimes influence the apparent used area. A workbook that is comfortable to scroll through may create many unexpected printed pages.

Review the source in print preview before conversion if you can. Define the intended print area, repeat necessary header rows and choose a sensible orientation. Check whether fitting everything onto one page makes the text too small. Sometimes several readable pages are a better result than one dense, technically complete sheet.

Inspect totals, displayed number formats and date formats in the exported PDF. Formula results can depend on supported functions and calculation behaviour. A visible value should be checked when it drives an important decision. The fact that the cell appears in the PDF does not prove that every source formula was interpreted as intended.

PowerPoint: a PDF is a static presentation

Slides can contain animation sequences, video, audio and interactive elements. A static PDF does not reproduce the live presentation experience. If an animation reveals several overlapping objects, the exported static state may not communicate the intended sequence. A video placeholder may remain without the media’s content.

Prepare a handout version when the live deck relies heavily on staged reveals. Replace essential motion with still frames or explanatory text in the source. Check charts, embedded objects and grouped shapes. A slide that works during a spoken presentation may need additional context when read independently as a PDF.

After export, compare the slide count and the order. Inspect the densest slide, a slide with a chart and a slide with unusual fonts. Check that objects near the edges have not been clipped. If the file is intended for printing, also review the reduced reading size in any N-up handout layout.

First-use engine downloads affect expectations

The local Office engine is substantial. Its first initialization can require a large download and noticeable time, even for a small input document. Later requests may benefit from browser caching, but memory and device performance still matter. A small source file does not mean the engine itself is small.

Use a stable connection for initialization and keep the tab open during processing. Avoid launching multiple heavy browser jobs at once. If a conversion times out, try a smaller representative document or a desktop device. Repeatedly pressing the operation button is not a useful remedy for a resource-constrained browser.

Distinguish setup failure from document failure. A blocked asset request or insufficient browser capability can prevent the engine from starting. A specific unsupported source feature may fail after the engine is already running. The stage and error message help identify which problem needs attention.

Build a representative comparison

For Word, select pages containing a table, an image, a section break and the final paragraph. For Excel, include the main table, repeated headers, a chart and the last printed page. For PowerPoint, choose slides with ordinary text, grouped graphics and media-dependent content. These samples are more informative than checking only the first page.

Compare the source’s intended output with the actual downloaded PDF. Count pages, inspect orientation and read important values. Look for changes in wrapping, clipping and symbols. If the document contains links or form-like content, test the behaviour that the recipient actually needs rather than assuming it survived because the label is visible.

For a formal submission, use the receiving organisation’s acceptance checklist. It may care about searchable text, embedded fonts, page size or an archival profile. A generic conversion success message does not establish compliance with those additional requirements.

Example: a spreadsheet budget attachment

Suppose a budget workbook has a summary sheet, detailed calculations and a chart. The recipient wants a readable PDF of the summary and chart, not every working cell. Configure or confirm the intended print areas in the source. Check totals and whether the chart legend remains meaningful in grayscale if printing is likely.

Convert and inspect the output. If the summary spills across several horizontal pages, fix the source’s print layout rather than merging the fragments and hoping the recipient understands them. If a total changes, investigate the source formula and converter support before sending the file. A layout problem and a calculation problem require different remedies.

Save the PDF with a delivery-specific name and retain the workbook separately. The PDF records displayed values and pages; it is not a substitute for the editable calculation model. If the recipient needs formulas, share the authorised source through the appropriate channel instead.

When to return to the source application

If a document depends on a specialised Office feature, exact corporate typography or a complex print setup, exporting directly from the authoring application may be the better route. A browser converter is useful, but it should not hide persistent differences by making broad fidelity promises.

Correct the source where possible instead of patching a converted PDF repeatedly. Source-level changes are easier to maintain and reproduce. Keep a short note of any conversion setting that materially affects the result, especially for recurring reports. That makes later discrepancies easier to diagnose.

Use Word to PDF, Excel to PDF or PowerPoint to PDF for the corresponding source type. If you need to go in the opposite direction, read the editable reconstruction guide first: recovering an editable file from fixed pages is a different and more uncertain task than exporting from an editable source.

A useful final check is to compare the opening and closing lines of each section across the source and export. This catches content that has slipped onto an unexpected page or disappeared below a print area. For workbooks, inspect the last populated row and column of every intended sheet. A visually attractive first page is weak evidence when the rest of a long document has not been checked.