What changed in LibreOffice 26.8
LibreOffice 26.8 was released on 26 August 2026 for Windows, macOS and Linux. The Document Foundation says development began in late 2025 and involved 206 contributors, including 155 volunteers. Typography is one of the release's main themes, alongside right-to-left script support and document exchange with other office suites.
The headline Writer change is the Paragraph Composer. The Foundation describes it as a text layout algorithm that balances word spacing across consecutive lines instead of handling each line separately. The Foundation's own announcement says the old approach is the greedy, single-line method that word processors have used for as long as the technology has existed. According to the announcement, that method produces justified text that alternates between crowded and sparse lines whenever long words land near a line break.
The feature belongs to the 26.8 major release. A hands-on piece from How-To Geek's David J. Buck tested it on 26.8.2, which is a bug-fix update to 26.8, not the release that introduced it.
Why justified text looks bad in the first place
Justified text stretches each line to meet both margins. The only elastic part is the space between words. When a long word won't fit, it drops to the next line. The line it left behind then has to absorb the slack, and you get a gappy line next to a tight one. Stack a few of those and the gaps can line up into visible channels down the paragraph.
Buck's account of older Writer versions matches this. He compared the same text left-aligned and justified in an older version and noticed a slightly wider stretch in the middle of the second line. That is his own observation from screenshots, not a measured test. It does illustrate the problem, and he says it became hard to unsee.
Looking at the whole paragraph gives the layout engine more options. It can pull a word up from the previous line, or push one down, so the spacing evens out across several lines. Debugpoint's review of the release puts it simply: Writer's justified text now has a control for it, and you can cap how wide that spacing is allowed to get.
The Knuth–Plass comparison, handled carefully
Buck notes that TeX typesetters have used the Knuth–Plass algorithm for decades. The idea behind it is well documented. Knuth and Plass's 1981 paper, "Breaking Paragraphs into Lines," says that, rather than making decisions one line at a time, the method treats the paragraph as a whole (this sentence paraphrases the paper's abstract). That way, the text on later lines can influence how an earlier line looks.
The comparison is useful context, but it has limits. The Foundation's material describes the Composer as balancing spacing across consecutive lines. Neither the release announcement nor the help page I reviewed says Writer's implementation is Knuth–Plass or equivalent to TeX. Treat it as the same broad principle, paragraph-level optimization, and not as a claim of identical output.
How to turn it on
The Writer help for 26.8 puts the control in the paragraph dialog. The steps below follow that help page and Buck's walkthrough:
- Select the paragraph or paragraphs you want to adjust. Alternatively, edit the paragraph style.
- Open Format → Paragraph and go to the Alignment tab.
- Set the alignment to Justified.
- In the Justification area, enable Paragraph Composer.
- Click OK and look at several consecutive lines, not just one.
The help page also says you can reach the Alignment tab through the sidebar's style editor (View → Styles, then New/Edit Style). That is the sensible route if you want the setting applied to a whole document through a paragraph style and not paragraph by paragraph.
Buck reports that enabling the option justified his text automatically, so pressing Ctrl+J afterwards was unnecessary. The official help doesn't state that as a rule. Check the alignment after you toggle the option and don't assume it.
The word-spacing controls still matter
The help page defines three word-spacing values, each expressed as a percentage of the width of a normal space character. Each accepts a value from 0% to 250%:
- Minimum: the tightest spacing Writer may use.
- Desired: the preferred spacing. The help recommends tuning this to prevent rivers and excessive hyphenation.
- Maximum: the widest spacing Writer may use.
Debugpoint says the release notes illustrate the feature with the same paragraph at 133% and 250% maximum word spacing. A tighter maximum forces the engine to find line breaks that avoid wide gaps. That means more rearranging, and possibly more hyphenation, if hyphenation is on.
What it won't do
The help page includes a qualification that the enthusiastic coverage tends to skip. The composer can remove excessive word spacing by shifting words from previous lines, but only if the new line breaks do not result in larger spacing than before (paraphrased from the Writer help). Put plainly, it is not a guarantee that every gap disappears. The help also says the best results depend on appropriate settings for limit, line width, microtypography and hyphenation.
Some practical consequences follow from that, and from general typesetting experience:
- Narrow columns give any justification algorithm little to work with.
- Long words and no hyphenation leave fewer legal break points.
- Left-aligned text doesn't have the stretched-spacing problem, so the Composer has nothing to fix there.
- Individual documents will vary. Buck's before-and-after screenshots are one person's view, not a benchmark.
A fair way to test it
To compare properly, take one justified paragraph and keep the font, page width and all other settings fixed. Toggle only the Paragraph Composer, and look at several lines in a row. If the text still looks loose, check the word-spacing values, the column width and the hyphenation settings before concluding the feature failed. This is my suggested procedure based on the documented controls, not Foundation-prescribed troubleshooting.
Pay particular attention to documents you share. Line breaks can change when the layout engine changes. A paragraph set with the Composer may break differently from the same paragraph opened in an older LibreOffice or in another application. Page counts and pagination could shift in documents that are tightly laid out. That is a reasonable expectation from how line breaking works, though I haven't seen the Foundation quantify it.
Which branch should you be on?
Buck's advice is simply to get the latest version. For a home user who cares about typography, that is reasonable. Production environments may see it differently. The Foundation's release-notes page labels the 26.8 line the "latest" branch for technology enthusiasts, which it warns may contain a few annoying bugs. It describes the 26.2 line as the mature branch, recommended for enterprises. On that page, 26.8.2 is dated October 29, 2026, and 26.2.7 is dated November 3, 2026.
The Foundation's announcement also says the 26.2 branch reaches end of life on 30 November 2026. So an administrator staying on 26.2 for stability has a clock running and will need a migration plan. The Foundation additionally points organisations deploying at scale to enterprise versions from companies in the LibreOffice ecosystem, which offer longer security-update horizons and support agreements.
Other 26.8 changes worth knowing
Typography is the headline, but the release has other changes that affect Windows users:
- Native OpenType variable font support, so variable fonts can be used as designed.
- A Draft view (View → Draft) that hides page layout for distraction-free editing, plus a baseline grid you can display.
- Changed alignment semantics: the Foundation says new documents default to start alignment rather than left, and that changing paragraph direction no longer mirrors explicitly left- or right-aligned paragraphs.
- Removed fonts: the obsolete Gentium Basic and Gentium Book Basic fonts are no longer bundled, so documents that specify them will substitute another typeface unless the fonts are installed separately.
- A donation banner in the Start Centre, shown periodically. The Foundation says it appears nowhere else in the software, and that LibreOffice has no advertising, telemetry or account requirement.
- Interoperability work: Neowin and the announcement both point to better OOXML handling, including round-tripping Microsoft Office chart types.
Bottom line
The Paragraph Composer is a worthwhile, narrowly aimed improvement. If you produce justified documents such as reports, newsletters or manuscripts, it is worth a few minutes of side-by-side testing. Expect better spacing balance, not typographic perfection. The documented limits are real, and results will depend on your text, your column width and your settings. For enterprise fleets, the more urgent 26.8 story is the approaching end of life of the 26.2 branch on November 30.