Keep checkable context when recovering and sharing files
Use repeated media references and trimmed track segments to understand why assets, usages and deletion policies belong in one handoff.
One PNG can have several usages
Extracting all Word images is a direct user task, but listing word/media paths loses document context. The checked sample reuses one PNG in body paragraphs2/3 and a header. The asset ZIP holds one payload while complete JSON preserves three actual references, helping a migration retain the required illustrations.
| Example | Complete evidence | Do not infer |
|---|---|---|
| Reused Word PNG | Same SHA256,three references,story/paragraph/XML path | Asset count equals use count or rendered page number |
| Embedded PPTX media | Original bytes,actual slide/shape,two relationship kinds | Two relationships mean two payloads |
| GPX circle deletion | Retained point indexes,two runs,deletion policies | Remaining tracks are certified anonymous |
Deleting points changes connectivity
Three middle points of the equatorial sample lie in the223m private circle. Removing100m at each end and dropping the waypoint leaves6 points. Joining them in one run invents a segment across the deleted area. Output retains two runs, routes split when needed, and the index report maps points back to their source. A fully deleted result is empty GPX rather than the original track.
Scope is part of the handoff
Original media means bytes actually stored in the Office package; data previously discarded by Office compression cannot be recovered. Default GPX reconstruction removes times, names, extensions and identifying metadata. Explicit time retention preserves those clues, and remaining locations can still reveal activities or identity. The operation implements deterministic trimming policies without anonymity certification.
- Deliver ZIP and complete JSON/CSV while retaining the source and policies.
- Check actual references or segment mappings before passing outputs onward.
- Use declared budgets and supported formats to assess scope; unknown semantics remain explicit context without invented page numbers or security conclusions.
References
- User task: extracting original Word images
First-person body read; evidence of the task, not market size.
- User task: recovering an embedded presentation video
Body read; recovering package bytes does not imply playback of every video format.
- User feedback: private zones and time removal
Body and cycling-group feedback read; task and anonymity guarantee are distinguished.
Tools in this category
Expand a tool to see its steps, options and supported formats, then open its workspace.
Recover original Office mediaRecover original DOCX, PPTX and XLSX media with document stories, slide shapes and worksheet drawing anchors.
Download original image, audio and video bytes in a ZIP with complete SHA256 and usage reports. Word uses stories and logical paragraphs, PowerPoint uses actual slide order and shapes, and Excel uses worksheet names and cell anchors. Other parts retain precise part/XML context; Word page numbers are not inferred.
Steps
- Choose an Office package.
- Inspect media counts and full report usage locations.
- Download original media ZIP and JSON/CSV.
Capabilities and limits
- One ordinary DOCX/PPTX/XLSX up to 30 MiB; 80 MiB expanded, 10,000 entries, 1,000 media assets and 20,000 references; total XML 20 MiB and 1,000,000 nodes.
- Legacy DOC/PPT/XLS, OLE, macros, encryption and signed packages are unsupported. Media and input code are never executed; external URLs are never fetched. External reports strip credentials, queries and fragments. Empty media produces a valid zero-asset report.
- OOXML transitional namespaces; Excel ordinary worksheets are supported, chartsheets are unsupported. Complete JSON/CSV each20 MiB; combined output100 MiB limit.
Remove private GPX locations and timesDelete explicit private zones and start/end distances, reconstruct GPX from selected fields and export segment mappings without private centres.
By default keep track/route coordinates and elevation; drop waypoints, times, metadata, names, extensions, original creator and all other fields. Explicitly retain valid point times or waypoints if needed. Circle deletion includes its boundary; removed points split track segments and routes. Download reports contain indexes and policies without private circle centres or removed coordinates.
Steps
- Choose GPX and define deletion circles or start/end distances.
- Confirm point, time and elevation policies.
- Inspect deletion counts and download the copy and index report.
Available options
- Deletion circles JSON
- []
Each item: {"lat":0,"lon":0,"radiusM":223}; up to20, radius0–1,000,000m. Centres are used only for local computation.
- Start metres per track/route
- 0
- End metres per track/route
- 0
- Point selection
- Tracks and routes · Tracks only · Routes only · Include waypoints · Waypoints only
- Point time policy
- Remove · Explicitly retain
- Elevation policy
- Retain · Remove
Capabilities and limits
- One GPX1.0/1.1 up to10 MiB, 50,000 points and2,000 segments;20 circles and1,000,000 point-circle checks; XML depth32 and200,000 nodes.
- Start/end distances accumulate separately per source track/route without connecting original gaps. Spherical Haversine R6,371,008.8m handles the date line. Coordinates/elevation use GPX decimal syntax; stored times must be valid and timezone-qualified. Deletion does not certify legal anonymity or prevent inference; retaining times preserves those clues.