Page breaks are useful when you want to force content onto a fresh page—like starting a new chapter or section. But sometimes they're unwanted artifacts left behind by editing, templates, or accidental keystrokes. Knowing how to identify and remove them is a practical skill that saves frustration and keeps your documents looking the way you intend.
A page break is an invisible formatting marker that forces the content after it to begin on a new page. It's different from simply reaching the end of a page naturally—page breaks are intentional commands embedded in your document.
There are two types:
You can only remove manual page breaks. Automatic ones reflow naturally as you edit.
Before you can remove a page break, you need to see it. Most word processors hide formatting marks by default.
In Microsoft Word:
In Google Docs:
In other programs (Apple Pages, LibreOffice):
Once visible, page breaks are easy to spot—they're distinct from the normal paragraph markers that appear throughout your text.
The process is straightforward once you can see the break.
In Word:
In Google Docs:
In other programs: Follow the same principle: select or position your cursor on the break, then delete it.
If you have multiple unwanted page breaks, removing them one at a time is the safest approach. It takes longer but prevents accidentally deleting actual content.
Different situations create page breaks:
Your reason for removing them doesn't change the process, but it helps explain why they're there in the first place.
Before mass-deleting page breaks, consider:
If you're unsure whether a break is intentional, it's worth checking the document's purpose first.
Removing page breaks is one of the easiest formatting tasks in word processing. The key is making them visible first, then deleting them one at a time. This approach gives you control and prevents unintended changes to your document's structure. For most everyday documents, this straightforward method works reliably—but for complex layouts or collaborative files, a moment of consideration beforehand saves rework later.
