🕵️ DeckMedic · Stealth & Scrub Suite · Tool 1 of 4

PPTX Metadata Wiper
Remove Author, AI Fingerprints & Edit History

Every PowerPoint file secretly stores your name, company, total editing time, and — if you used Copilot or ChatGPT — custom session IDs in hidden XML fields. This tool physically removes all of it before you share or submit the deck.

🔒

Zero upload

File stays on your device

⚡

Instant

No server round-trip

🆓

Free

No sign-up required

📄

PPTX only

Accepts .pptx files

📂

Drop your .pptx here

or click to browse

Runs 100% in your browser — file never leaves your device

What this tool actually does

← drag handle to compare  ·  left = before  ·  right = after →

✕ Before
  • AuthorSarah Chen
  • CompanyMeridian Consulting LLC
  • Edit time7 min
  • Custom propsGptSessionId detected
✓ After
  • AuthorMicrosoft Office User
  • Companycleared
  • Edit time187 min (randomized)
  • Custom props3 entries deleted
📖 How this tool works · Tips · Browser Privacy

Metadata Wiper — How it works

  1. 1

    Open & drop

    Open Metadata Wiper in any modern browser. Drag your .pptx file onto the drop zone — or click to browse. No sign-in needed. Files never leave this tab.

  2. 2

    XML surgery — on your device

    JSZip reads the PPTX container locally. docProps/core.xml has dc:creator and cp:lastModifiedBy set to Microsoft Office User. docProps/app.xml gets TotalTime randomized to 120–420 minutes and Company cleared. docProps/custom.xml (Copilot session IDs) is physically deleted along with its [Content_Types].xml entry.

  3. 3

    Download instantly

    The sanitized PPTX is rebuilt in memory and offered as a download named _clean_meta.pptx. The Before/After audit table shows every field that was changed. Closing the tab discards all data.

Fields modified

dc:creator

core.xml — Set to "Microsoft Office User"

cp:lastModifiedBy

core.xml — Set to "Microsoft Office User"

cp:keywords

core.xml — Cleared (may contain AI model names)

dc:description

core.xml — Cleared

TotalTime

app.xml — Randomized 120–420 minutes

Company

app.xml — Cleared

docProps/custom.xml

ZIP — Physically deleted (Copilot session IDs)

Tips

  • → Run this before uploading to client portals, RFP systems, or academic submission platforms — they all parse PPTX metadata.
  • → Check the Before/After table. Fields that show "—" in the Before column were already blank — no risk there.
  • → Combine with Hidden Slide Killer to prevent clients from unhiding internal commentary slides.
  • → Google Slides exports and Canva downloads do not embed the same metadata fields — this tool is specifically for native .pptx files.

Privacy & data security

🚫

Zero upload

No file ever sent to a server

📴

Works offline

After first page load

🔇

No telemetry

File data never logged

✅

GDPR safe

No data processor needed

Browser compatibility

Chrome 112+Edge 112+Firefox 111+Safari 16.4+iOS Safari 16.4+Chrome Android 112+

Stealth & Scrub Suite · You might also need

🙈

Hidden Slide Killer →

Physically terminate hidden slides so clients can never unhide them.

 🔏

PII & Comment Scrubber →

Redact emails, phone numbers, and credit cards from speaker notes.

 🔍

Lorem Ipsum Hunter →

Scan every slide for TBD, TK, [INSERT] and lorem ipsum before sending.

Who uses Metadata Wiper

🏢

Management Consultants

MBB and Big 4 consultants run Metadata Wiper before client delivery to remove firm templates, analyst names, and Copilot generation records — especially on M&A and strategy decks where authorship is sensitive.

⚖️

Law Firms & Legal Teams

Attorneys use Metadata Wiper before filing exhibits and submitting discovery materials. PPTX metadata revealing AI usage or dual-firm collaboration can create disclosure obligations under court rules.

🎓

Students & Academics

Students submitting presentations to academic integrity platforms use Metadata Wiper to remove AI tool signatures from docProps/custom.xml before submission to avoid automated flags on Turnitin and iThenticate.

🏛️

Government & Defence

Public sector teams strip metadata before FOIA-visible file submissions and inter-agency sharing where document provenance could be exploited through metadata analysis by adversarial parties.

Metadata Wiper vs alternatives

Feature DeckMedic Wiper PowerPoint Document Inspector iLovePDF Metadata
Upload to server ❌ Never❌ Never (desktop app)⚠️ Always (cloud)
Removes Copilot session IDs ✅ Yes — deletes custom.xml⚠️ Partial only❌ No
Before/After audit report ✅ Full field diff❌ None❌ None
Works in browser (no install) ✅ Yes❌ Requires desktop Office✅ Yes
Randomizes TotalTime ✅ Yes (2–7 hours)❌ Just removes❌ No
Free tier ✅ Unlimited✅ Free (with Office 365)⚠️ 5 files/day
GDPR / zero data transit ✅ No transit at all✅ No transit❌ EU/US servers

Frequently asked questions

How do I remove my name from a PowerPoint file?
Open DeckMedic's free Metadata Wiper. Drop the file — the tool reads docProps/core.xml, replaces dc:creator and cp:lastModifiedBy with "Microsoft Office User", and outputs a clean download in seconds. No PowerPoint installation needed.
Does PowerPoint record who made the file?
Yes. Every PPTX stores the original author, last modifier, company name, total editing time, and — if Copilot was used — custom session IDs in docProps/custom.xml. These persist through Save As and are visible in File → Properties → Advanced Properties.
How do I remove Copilot metadata from a PowerPoint?
Microsoft 365 Copilot stores generation records in docProps/custom.xml as custom XML properties. DeckMedic physically deletes this file from the PPTX ZIP container, along with its Override entry in [Content_Types].xml. The audit table confirms removal.
What is TotalTime in a PPTX file and why does it matter?
TotalTime (in docProps/app.xml) records cumulative editing time in minutes. A freshly AI-generated deck often shows TotalTime=2, which signals automated generation. Metadata Wiper randomizes this to a realistic 120–420 minutes.
Does this tool work without uploading the file?
Yes. Metadata Wiper processes the PPTX entirely in your browser using JSZip. The file is read directly from your device into browser memory — zero bytes are transmitted to any server or API endpoint.