Recover Office media and share GPX under explicit policies
Check original media usage locations, remove explicit private track zones and retain complete outputs and field policies.
Choose the actual handoff
Word users need embedded images, and presentation users may need an embedded video whose original file is missing. These tasks need actual package bytes. Screenshots or re-encoded copies do not establish original recovery. T267 provides SHA256 and usage locations so repeated references remain checkable.
| Input | Usage location | Complete deliverable |
|---|---|---|
| DOCX | Body/header/footer/comment/note story, logical paragraph and table XML path | Original-byte ZIP, SHA256 and complete usage JSON/CSV |
| PPTX | Actual slide order, shape ID/name; explicit context for other parts | Original image/audio/video bytes and relationship report |
| XLSX | Ordinary worksheet name, drawing cell/absolute anchor | Original package images and anchor mappings |
| GPX | Original track/route/waypoint and output segment indexes | Minimal reconstructed copy, deletion policies and index report |
Distinguish media assets and references
The checked Word example uses one PNG in body paragraphs2/3 and a header. One PNG suffices, but all three locations must remain. PowerPoint can have both video and media relationships for one payload; they are not two original assets. Excel B2/D4 anchors resolve through their source worksheet relationships. Package thumbnail root relationships are also reported.
Word page numbers depend on layout and cannot be inferred from logical paragraphs. Unknown parts retain explicit XML context. Limits are30 MiB input,80 MiB expanded,1,000 assets and20,000 references. Legacy Office/OLE, macros, encryption, signatures, strict namespaces and Excel chartsheets are unsupported. External links are never fetched and original media is never executed; empty media yields an accurate report.
Reconstruct a track sharing copy
Default output keeps track/route coordinates and elevation while dropping waypoints, point times, metadata, names, extensions, original creator and other unknown fields. Explicitly retain valid times or waypoints, or remove elevation. Circle JSON lat/lon/radiusM is used only locally and is absent from download reports; removed coordinates are absent too.
The checked sample has11 equatorial track points and1 waypoint. Removing100m at each end and a223m circle retains6 points in2 segments. Deleted points never create a new connecting line; routes split into separate routes. Start/end distances sum original adjacent edges per track/route without bridging original gaps. Spherical Haversine uses radius6,371,008.8m, deletes the circle boundary and handles the date line.
Check outputs and recover
GPX limits are10 MiB,50,000 points,2,000 segments,20 circles and1,000,000 point-circle checks. Coordinates/elevation follow GPX decimal syntax; retained times must be valid and timezone-qualified. Deleting all points still returns valid empty GPX and a zero-point report, never the sensitive original.
- Verify media SHA256, actual references and required assets; retain complete downloads rather than treating the200-row preview as the total.
- Check GPX point selection, time/elevation policies, deletion counts and segment mappings.
- Remaining locations or retained times may reveal identity; the tool does not certify legal anonymity or prevent inference.
- Correct CRC failures, missing relationships, invalid coordinates or budgets and rerun; a rejected input is not a successful empty output.
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.