When a large Writer document starts pausing as you type, scrolling may stutter, images may redraw slowly, or saving may take much longer than before. The page count alone does not identify the cause. A file with a few enormous photographs can behave differently from a longer text-only file, and a slow save can point to a different bottleneck than a slow cursor.
Work on a copy before changing image data or resetting settings. Then test one change at a time and repeat the same actions in the same part of the document. That gives you useful evidence instead of a collection of tweaks with unknown effects.
Writer has to lay out text and page objects as content changes. Images add data to load and display, and their size, quantity, placement, and text wrapping can affect how much work the application does. This is a practical diagnosis, not a universal rule: the same document may run smoothly on one computer and lag on another because memory, storage speed, graphics drivers, and LibreOffice configuration differ.
A large file size can make opening and saving take longer, but it does not prove that file size is the only cause of typing lag. Likewise, reducing zoom is a quick display test, not a guaranteed fix. First identify whether the delay happens while opening, typing, scrolling, or saving.
Use File > Save As to create a working copy, or duplicate the file through your operating system. Keep the original unchanged. If the document is stored on a network share or synced folder, make a local copy and compare it; this helps distinguish Writer work from storage or sync delays.
In each copy, note four timings or observations: time to open, time for the first few keystrokes to appear, smoothness while scrolling through an image-heavy section, and time to save. Keep the test small and repeatable. For example, type the same short sentence, scroll to the same page, then save. Close other heavy applications if system memory is under pressure, but do not assume that more memory alone will solve the issue.
Useful signal: if typing is responsive but saving is slow, investigate embedded image size and the storage location first. If typing and scrolling are slow even on a local copy, continue with display and document tests.
On the test copy, choose View > Images and Charts to hide graphical objects temporarily. Writer shows empty frames in place of hidden images. This setting changes what is displayed while editing; it does not remove the image data from the document.
Try the same typing and scrolling test with images hidden, then turn them back on before judging the document’s final appearance. If the editor becomes noticeably more responsive with images hidden, graphics display or the graphics workload is a plausible contributor. If there is little change, the slowdown may come from another source, such as document layout complexity, extensions, the user profile, or storage.
For a smaller display test, use the zoom control and single-page view on the Writer status bar. The status bar offers zoom and page-layout controls. If lower zoom or single-page view helps, keep the setting that is comfortable for editing, but remember that this is a viewing adjustment rather than image optimization.
See the official Images and Charts command and Writer status bar guide for the documented controls.
Photos often have far more pixels than a printed page or on-screen document needs. In your copy, select an image and open Format > Image > Compress, or use the image’s context menu and choose Compress. The dialog can adjust JPEG quality and image resolution. LibreOffice Help currently describes the JPEG quality scale from 0 to 100 and allows you to change an image’s dimensions.
Choose settings according to how the document will be used. A report viewed on screen may not need camera-original dimensions; a publication or archival document may need higher resolution. Preview the result and retain a separate original if image quality matters. Compression can be lossy, and even a smaller document is not guaranteed to fix typing lag if the cause is elsewhere.
PNG compression is lossless, so lowering its compression setting is not the same as reducing pixel dimensions or using lossy JPEG compression. Do not expect every PNG to shrink substantially. After changing images, save the copy, close and reopen it, and compare both the file size and your original responsiveness test. The official Compress Image help page explains the quality and resolution controls.
If image hiding and sensible image resizing do not explain the lag, run LibreOffice’s Troubleshoot Mode. In current LibreOffice Help (26.8), this mode starts with a temporary user profile and disables hardware acceleration. Choose Help > Restart in Troubleshoot Mode, then select Continue in Troubleshoot Mode to test the same document and actions. Changes made in the temporary profile are discarded when you restart normally.
If the document responds better in Troubleshoot Mode, that is evidence that the regular profile, a user extension, or graphics acceleration may be involved; it does not identify which one. Exit to normal mode and use the mode’s guided options to test changes gradually. Avoid resetting the entire profile as a first step because it can remove settings and customizations. If performance is worse or unchanged in Troubleshoot Mode, restart normally and focus on the document, system resources, or storage instead.
Read the official Troubleshoot Mode documentation before applying profile resets. The current help page notes that full profile resets are more extensive and should be reserved for cases where less disruptive tests fail.
Use a current stable LibreOffice release supported for your operating system, especially if the lag began after an upgrade or affects one file type. The Help pages linked above describe LibreOffice 26.8 at the time of research. An update can include performance fixes, but a newer version is not proof that every large image-heavy document will become fast. After updating, reopen the same test copy and repeat your baseline checks.
If you routinely exchange the file as DOCX, make a separate ODT test copy and compare it in Writer. Treat that as a diagnostic comparison, not a promise that conversion will fix performance: file-format conversion may change layout or object behavior. Keep the format required by collaborators for the delivery copy, and inspect page breaks, image wrapping, and captions after any conversion.
When the file is stored on a slow external drive or network location, test from a local disk and save back only after editing. If the local copy is faster only during opening and saving, storage is a stronger suspect than image drawing. Do not unlink images as a shortcut unless you have a reliable plan to keep every linked file available; linked images are reloaded from their source when the document is updated and loaded, as described in the official Insert a Graphic From a File guide.
| Claim | What the test can actually show | Next action |
|---|---|---|
| “The document is long, so Writer must be out of memory.” | Page count alone does not reveal memory pressure or the cause of lag. | Compare typing, scrolling, opening, and saving separately; check system resource use during the slow action. |
| “Hiding pictures makes the file smaller.” | View > Images and Charts hides objects on screen; it does not remove their data. | Use the Compress command on a copy if reducing embedded image data is appropriate. |
| “A smaller file guarantees faster editing.” | Smaller data may help loading or saving, but other layout or graphics issues may remain. | Repeat the same responsiveness test after each change. |
| “Resetting everything is the quickest fix.” | A clean temporary profile is a diagnostic comparison; a full reset can discard preferences. | Try Troubleshoot Mode first and change one setting or extension at a time. |
Reopen the edited copy and repeat the same four checks: opening, typing, scrolling, and saving. Confirm that important images remain sharp at the intended print or screen size, captions and wrapping still look right, and the file opens from its normal storage location. If only one check remains slow, keep investigating that stage instead of repeating unrelated fixes. If the problem persists in a local copy and Troubleshoot Mode, note your LibreOffice version, operating system, file type, approximate file size, and the exact action that pauses; those details make a support request or bug report more useful.
Create an Outlook meeting invite, add required or optional attendees, choose a time, add Teams details, set recurrence, and check replies in new or classic Outlook.
Use Excel's Data Validation settings to set a maximum, minimum, exact length, or character range, then add clear prompts and error alerts.
Fix the Outlook “We can’t schedule the meeting” error by checking account support, refreshing Teams sign-in, and repairing the Classic Outlook add-in.
Change Office 365 menus, spelling and grammar settings, or keyboard input in desktop apps and Microsoft 365 for the web.
Learn how to auto-forward all or selected emails in Outlook 365 using Forwarding settings or Rules, plus how to stop forwarding and fix blocked external forwards.
Use Microsoft Editor in Word for Microsoft 365 to check spelling, grammar, clarity, and conciseness, review suggestions, and tune proofing settings.
Learn how to add an RSS feed to Outlook 365 in classic Outlook for Windows, find the correct feed URL, manage subscriptions, and fix common RSS issues.
Jump straight to any page in Word for Microsoft 365 with Ctrl+G or F5, relative page numbers, or the Navigation pane, with Windows and Mac shortcuts.
Learn how to add contacts to Outlook on the web, new Outlook, classic Outlook, and mobile, plus how contact syncing and CSV imports work.
Change a Word page color, add a picture background, remove either, and enable background printing on Windows or Mac with clear, current steps.
