{{ summaryTitle }}
{{ summaryValue }}

{{ summaryLine }}

Profile:{{ profile.label }} Privacy:Local only Warnings:{{ computation.values.warning_count }}
{{ summaryAnnouncement }}
DOCX compression inputs
{{ sourceFile ? sourceFile.name : 'Drop one DOCX here' }}
{{ sourceFile ? fileMeta : 'or browse for a local Word document' }}
{{ fileError }}
Compact favors size, Balanced favors everyday documents, and Print retains more image detail.

{{ workflowMessage }}

The neutral default keeps the preview and does not alter the normal compression result.
{{ params.remove_thumbnail ? 'Remove preview when present' : 'Keep preview thumbnail' }}
DOCX file
{{ resultBadgeLabel }}
{{ artifactLabel }}
SHA-256 {{ outputSha256.slice(0, 12) }}…
{{ row.label }}{{ row.value }}
Image optimization can be lossy. Keep the original and review important pages in Word; package verification does not render Word layout.
{{ chartExportStatus }}

The chart renderer is unavailable. Exact package sizes remain in the other artifacts.

{{ tableExportStatus }}
Package part or checkDecisionBeforeAfterEvidenceCopy
{{ row.label }}{{ row.decision }}{{ row.before }}{{ row.after }}{{ row.detail }}

A DOCX file is a ZIP-based document package. Its visible pages come from XML, styles, relationships, fonts, media, headers, footers, and other parts stored together. Recompressing the container can save some space, but large embedded photographs and screenshots are often the main reason a document remains heavy.

Image optimization is effective because Word usually displays an image at a fraction of its original pixel dimensions. Reducing an oversized JPEG or PNG can cut many bytes while leaving text and document structure editable. The tradeoff is visual: JPEG recompression is lossy, and resizing can soften fine labels, signatures, diagrams, or print detail.

DOCX content and compression treatment
Package content Compression treatment
Referenced JPEG and PNG images Eligible for resizing and same-format re-encoding when the replacement is materially smaller.
Document XML, styles, headers, footers, and ordinary relationships Repacked but otherwise preserved byte-for-byte.
Unsupported image formats and embedded objects Kept unchanged and reported as warnings where relevant.
Optional package preview thumbnail Removed only when selected and not shared by another relationship.

Package integrity and visual fidelity are different checks. A rebuilt file can contain the expected parts, valid relationships, and valid image data while still showing a changed crop, softened screenshot, or altered page break in Word. The original should be retained until the compressed copy has been opened and important pages have been reviewed.

Not every document will shrink. If eligible images are already compact, the rebuilt package may equal or exceed the source size. In that case, keeping the original is safer than delivering a “compressed” file with no byte advantage.

How to Use This Tool:

Work from a copy of the document and choose the image profile for its final use, not merely for the smallest possible number.

  1. Choose one unsigned DOCX file without macros, no larger than 25 MB.
  2. Select Compact for screen sharing, Balanced for everyday documents, or Print when image detail matters more than maximum reduction.
  3. Leave Document preview thumbnail set to keep unless removing that package preview is intentional. Word may create a new preview after a later save.
  4. Select Compress DOCX and let the package inspection, image decisions, rebuild, and verification finish.
  5. Read the optimization ledger and preserved-feature warnings. If the result says No gain, keep the original because the rebuilt package is discarded.
  6. Open a downloaded result in Word and inspect image-heavy, signed-off, or print-critical pages before replacing or sharing the source.

Interpreting Results:

Savings percent compares final package bytes with source package bytes. Images optimized counts media parts that were actually replaced; unsupported, unchanged, or larger candidate images remain in the package without contributing to that count.

  • Optimized means the replacement was at least 1 KiB smaller than its source.
  • Candidate larger · kept means re-encoding did not create enough savings, so the original image bytes were retained.
  • Preserved feature warns about content such as embedded objects, ActiveX parts, external relationships, or unsupported image formats that was kept rather than optimized.
  • ZIP integrity and relationship checks prove package-level consistency, not rendered Word layout.

A smaller verified package is a candidate output, not the new master by default. Compare the pages that carry the most visual or legal consequence before accepting it.

Technical Details:

Office Open XML uses Open Packaging Conventions to connect package parts through typed relationships. Compression begins by loading every part with CRC32 checking, resolving internal targets, finding the main Word document, and identifying referenced media. The rewrite changes only selected JPEG or PNG parts and, when requested, an unshared preview thumbnail plus its package records.

Formula Core

Measured savings never reports a negative value. Percentage savings is calculated from exact package byte counts and rounded to two decimal places for display.

Saved bytes = max(0,Bsource-Boutput) Savings percent = round ( Saved bytes×100Bsource ,2 )

A 1,000,000-byte source rebuilt to 600,000 bytes saves 400,000 bytes, or 40%. If output is equal to or larger than source, the outcome is No gain and no replacement DOCX is offered.

Transformation Core

DOCX image profile and rewrite rules
Profile Maximum image edge JPEG quality Use
Compact1,280 px72%Smaller screen-oriented documents
Balanced1,920 px82%General sharing and editing
Print2,560 px90%Higher-detail output

Images larger than the profile edge are resized proportionally. JPEG files of at least 100 KiB may also be re-encoded at the profile quality even when no resize is needed. PNG files keep PNG encoding and transparency. A candidate replaces the original only when it is at least 1,024 bytes smaller.

The rebuilt archive uses maximum DEFLATE compression for package parts. It is then reopened with CRC32 verification. Expected part names, required Word content types, internal relationship targets, and changed image signatures are checked; every unselected part must remain byte-identical.

Rule Core

DOCX processing limits and exclusions
BoundaryRule
Package entries3 through 500 file parts, with at most 120 MiB expanded data
Supported image targetsAt most 40 referenced JPEG or PNG parts
Decoded pixelsAt most 24 million per image and 80 million across supported images
Generated packageAt most 30 MB and must finish within 45 seconds
Macro-enabled packageRejected
Digitally signed packageRejected because rewriting would invalidate the signature

Removing a preview thumbnail changes its root relationship and content-type record only when the thumbnail is not shared. Other media and package features remain outside that optional cleanup.

Limitations and Privacy:

The document stays in the browser tab during inspection and rewriting; it is not uploaded for processing. Image conversion can still be lossy, and package verification does not render pages as Microsoft Word does.

  • Keep the original until the compressed copy opens correctly and important pages have been visually reviewed.
  • Embedded objects, ActiveX parts, external relationships, and unsupported images are preserved rather than interpreted or optimized.
  • Digital signatures and macro-enabled packages are not rewritten.
  • A later Word save may recreate a removed preview thumbnail or rewrite other package parts.

References: