Skip to main content
PDF4me APIIntegrationsKnowledge BaseExtensionsAPI TesterBlog

Optimize Word Documents in Make

What this module does

PDF4me — Optimize Document compresses a Word document inside a Make scenario and returns a smaller, cleaner file without modifying the original. Choose from three optimization levels: Low preserves almost everything with 0–10% size reduction; Medium removes comments, hidden content, macros, and personal info while compressing images to 60% quality (50–80% smaller); High applies aggressive cleanup including revisions and unused styles (80–90% smaller). Use it to stay under email attachment limits, cut cloud storage costs, or prepare documents for archival.

Authenticating Your API Request​

Every PDF4me module in Make requires a valid Connection. Create or select one that holds your PDF4me API key so the scenario can authenticate document optimization requests securely.

Get your API Key

Important Facts You Should Not Miss​

Three Distinct Levels
Low (0–10%) keeps revisions and formatting intact — best for documents still in review. Medium (50–80%) removes comments, macros, and personal info — ideal for email distribution. High (80–90%) also strips revisions and unused styles — use for archival.
Medium Is the Default
Medium balances size and quality — it compresses images to 60%, removes hidden content, cleans metadata, and is the best choice for email distribution. If you do not set Optimization Level, the module defaults to Medium automatically.
Original Is Never Modified
The module outputs a new optimized file in Doc Data. The document you pass in is untouched — save the output to a separate folder or filename if you want to keep both the original and the compressed version.
Optimize Document Word module in Make – compress .docx file size with PDF4me

PDF4me Optimize Document module compressing a Word document in a Make scenario.

Parameters​

Required: Connection, File Name, and Document. Optimization Level defaults to Medium if not set. Culture Name is optional.

ParameterRequiredWhat it doesExample
ConnectionYesPDF4me API connection. Click Add and paste your API key if connecting for the first time.Your PDF4me connection
File NameYesWord document filename with .docx or .doc extension — used for output file naming.report.docx
DocumentYesBinary Word document mapped from a preceding module such as Google Drive Download or Dropbox Get File.[Buffer from Get File]
Optimization LevelNoControls aggressiveness of size reduction. Low (0–10%), Medium (50–80%, default), or High (80–90%). Defaults to Medium if not set.Medium
Culture NameNoLocale code for document processing — affects language-sensitive content handling.en-US

Quick Setup​

  1. Add PDF4me → Optimize Document to your Make scenario.
  2. Select Connection (or click Add to create one with your PDF4me API key).
  3. Map the Word document binary from a preceding module and set File Name (with .docx extension).
  4. Set Optimization Level — leave blank or choose Medium for the best balance of size and quality.
  5. Run the scenario — the Doc Data output contains the optimized Word file ready to save to your destination storage.

Workflow Examples​

Workflow ExamplesCommon Make scenario patterns using Optimize Document.
Email-ready document distribution
  1. Google Drive New File trigger detects a new Word report uploaded by the team.
  2. Optimize Document (Medium) reduces the file from 20 MB to under 5 MB.
  3. Gmail Send Email attaches the optimized Doc Data output — well within attachment limits.
  4. The recipient receives a clean, compact file without any manual compression steps.
Monthly cloud storage cleanup
  1. Scheduled trigger lists all files over 5 MB in a Dropbox folder.
  2. Iterator loops through each file — Get File → Optimize Document (High).
  3. Dropbox Upload overwrites the original with the compressed version.
  4. Aggregator tallies total bytes saved — Slack posts the monthly storage report to the team.
Project archive with privacy cleanup
  1. Airtable detects a project marked as Closed and triggers the scenario.
  2. Get project documents from SharePoint, then Optimize Document (Low) strips personal info (author, company).
  3. SharePoint Archive uploads the cleaned files to long-term cold storage.
  4. Low level preserves image quality and layout while satisfying GDPR compliance requirements.

Frequently Asked Questions​

Which Optimization Level should I choose?+
Use Low when you need to preserve tracked changes and formatting — for example a document still in review. Use Medium (default) for email distribution or sharing — it removes clutter while keeping all visible content. Use High for storage archival when you no longer need revision history, macros, or unused styles.
Does optimization change the document visual appearance?+
Low and Medium preserve all visible layout and content. High may adjust formatting by removing redundant styles, but the core text, headings, and structure remain intact. All levels compress images — at 80%, 60%, and 50% quality respectively.
What personal information is removed?+
Medium and High levels remove document metadata including author name, manager, and company name stored in Word document properties. This supports GDPR compliance and is recommended before sending documents to external recipients.
Does High level remove tracked changes?+
Yes — High Optimization Level removes revisions (tracked changes). Low and Medium preserve the full revision history. If tracked changes need to be retained for legal, compliance, or review purposes, use Low or Medium instead.
Is the original document modified by this module?+
No. The module returns a new optimized file in the Doc Data output field. The document you pass in is never changed. Upload the optimized output to a separate folder or filename if you want to keep both the original and the compressed version.

Get Help​

Make IntegrationGet your API KeyMake Documentation