> Disclosure: ExtractPhone is developed by Octo Digital Forensics, the parent company of Digital Forensics Today. I’m Derick Downs — I run both organizations. This review reflects my genuine assessment of the product, including its real limitations, but readers should be fully aware of this relationship before weighing my perspective. I’ve tried to write this the same way I’d write it if someone else built it.
Writing an honest review of something you helped create is harder than it sounds.
The temptation is to oversell. To lead with the wins and footnote the gaps. I’m not going to do that here, partly because it’s bad practice and partly because the practitioners who read Digital Forensics Today are smart enough to see through it.
So here’s the real picture on [ExtractPhone](https://extractphone.com): what it actually does, where it does it well, and where we still have work to do.
What ExtractPhone Is and Why We Built It
ExtractPhone came out of a problem I kept running into in civil forensic work.
After a mobile device extraction — whether from Cellebrite, Oxygen Forensic Detective, or any other tool — the raw output is not attorney-friendly. You get massive report exports, SQLite databases, XML files, thousands of images. The data is technically complete. It’s also largely incomprehensible to anyone who hasn’t spent years reading forensic output.
Attorneys need to understand the evidence. Clients need to understand it. Judges need to understand it. And when investigators hand over a 900-page PDF report or a folder full of CSV files, that understanding doesn’t happen — at least not efficiently.
ExtractPhone was built to solve the presentation and organization problem, not the extraction problem. It doesn’t extract data from phones. It takes data that’s already been extracted and makes it workable for investigation review, attorney collaboration, and evidence presentation.
That distinction is important and I’ll come back to it.
Core Capabilities: What ExtractPhone Actually Does
Evidence import and organization:
ExtractPhone ingests exports from major forensic platforms — UFED XML exports, Oxygen Forensic Detective exports, and raw SQLite databases from common iOS and Android apps. Once imported, the data is organized by artifact category in a clean interface designed for non-forensic users as well as examiners.
The import process is the first place I’ll be honest about a limitation: not all export formats from all tools are supported yet. UFED and Oxygen Detective exports work well. Some less common export formats require manual preparation before import. We’re adding support continuously, but if you’re running a less common extraction platform, test the import before assuming it works.
Communication timeline viewer:
This is the feature attorneys respond to most. ExtractPhone builds a chronological conversation view across all communication channels present in the extracted data — SMS, iMessage, WhatsApp, email — merged into a single timeline.
For matters where communication sequence matters (and it usually does), this saves hours of manual work. An attorney can see, in order, how a conversation developed across different apps, without jumping between separate report sections.
The timeline view supports date range filtering, sender/recipient filtering, and keyword search. For a three-month iMessage thread that’s central to a case, filtering down to the relevant week and exporting that subset is a 30-second operation.
Media gallery with metadata:
Photos and videos from an extraction are presented in a gallery view with embedded metadata displayed — capture timestamp, GPS coordinates where present, device identifiers, and file integrity information. Selecting images for inclusion in a case packet is drag-and-drop.
In property damage, personal injury, and custody matters where photo evidence is significant, this beats pulling individual images from a flat folder structure and manually logging metadata.
Case packet export:
ExtractPhone generates structured case packets — PDF or HTML — that present selected artifacts with context. The format is designed for attorney distribution and court filing: each artifact is labeled with source information, timestamp, and chain of custody notes carried forward from the original extraction.
This is where I see the biggest practical time savings in civil practice. Taking a completed extraction and preparing a 40-page attorney-ready evidence summary used to take me half a day. With ExtractPhone, it takes about an hour.
Annotation and tagging:
Examiners can annotate artifacts directly in ExtractPhone — flagging specific messages, adding investigation notes, tagging artifacts by relevance category. These annotations travel with the artifact through the export process, so the attorney receives the document with the examiner’s context embedded.
What It Does Well: The Honest Version
The communication timeline genuinely works. I’ve shown it to attorneys who’ve been doing discovery for 20 years, and the response is consistently the same: “Why hasn’t this existed before?”
The media gallery with metadata context is also strong. For cases where photo evidence is central — personal injury, insurance claims, property disputes — being able to present photos with verified timestamps and GPS data in a clean interface is a real advantage over handing over a folder of JPEGs.
The case packet export quality is solid for civil work. The PDFs are professionally formatted, the artifact sourcing is clear, and the documents hold up to basic attorney review without requiring forensic expertise to interpret.
The interface doesn’t require forensic training to use for review purposes. That means attorneys and clients can do their own preliminary review of the evidence without an examiner babysitting the process. This is either a feature or a risk depending on how you think about it — I’ll address it below.
Where It Has Room to Grow
I promised honesty. Here it is.
Import compatibility is the biggest current gap. ExtractPhone handles the major platforms well, but the forensic tool ecosystem is fragmented. If a practitioner is using a less common extraction tool or a custom export format, they may hit an import wall. We’re building toward broader format support, but we’re not there yet.
Deleted data handling is limited by design — ExtractPhone organizes and presents data from a completed extraction. If the extraction tool recovered deleted artifacts, ExtractPhone can display and organize them. But it doesn’t independently perform deleted record carving. This is a scope decision (ExtractPhone is a presentation layer, not an extraction engine), but practitioners should understand it clearly.
The non-forensic-user access question. Because the interface is intentionally approachable, there’s a risk that attorneys or clients use it to interact with evidence without understanding what they’re looking at. An examiner should always remain the primary steward of forensic evidence. ExtractPhone is a communication tool, not a substitute for forensic expertise.
Search sophistication is functional but basic. Keyword search works. Regex and boolean search are in development. For large-volume investigations where complex search logic matters, you’re currently supplementing with external search tools.
Multi-device case management — cases involving 10+ devices with large cross-device artifact volumes — starts to feel heavy in the current version. Performance improvements for large case loads are on the development roadmap.
No automated chain of custody generation. ExtractPhone carries forward chain of custody information from the original extraction but doesn’t auto-generate its own acquisition documentation. This is by design (ExtractPhone doesn’t do the acquisition), but it means the examiner’s documentation from the extraction phase needs to be thorough and maintained separately.
How It Fits in a Civil Forensic Workflow
Here’s the workflow where ExtractPhone actually adds value:
- Extraction with your primary forensic tool ([Cellebrite UFED Premium](/cellebrite-ufed-premium-field-evaluation/), [Oxygen Forensic Detective](/oxygen-forensic-detective-review/), [MOBILedit Forensic Express](/mobiledit-forensic-express-review/), or others).
- Export from the forensic tool in a supported format.
- Import into ExtractPhone and organize artifacts by relevance, category, and case theory.
- Annotate key artifacts with investigator notes and relevance flags.
- Collaborate with the attorney — share access for their review, or generate a case packet for distribution.
- Export case packet for court or settlement preparation.
ExtractPhone doesn’t replace any step before step 3. If you’re looking at it as an extraction tool, you’re misreading what it is.
Where it earns its place is steps 3–6. The organization, annotation, collaboration, and presentation functions are real time savers that translate to real money saved for the client and real capacity freed up for the examiner.
Pricing and Access
ExtractPhone pricing is published at [extractphone.com](https://extractphone.com). As the parent company, I can confirm the current model — but I’d encourage you to check the site directly for current pricing since it has evolved since initial launch and may continue to.
The pricing model is case-based rather than annual seat licensing, which reflects the civil practice reality that case volume varies significantly. You’re not paying for a year of access when you have three active cases; you’re paying per matter.
For solo practitioners and small firms where 10–15 civil forensic matters per year is a normal volume, this structure works well. High-volume labs doing 50+ cases per year should contact us directly about volume arrangements.
The Competition Question
I won’t pretend there’s no competitive landscape here. Magnet’s AI Review and some features in Physical Analyzer cover adjacent territory — organizing and presenting extracted artifacts for attorney review. Nuix Workstation does this at an enterprise level for larger eDiscovery workflows.
Where ExtractPhone aims to be different: price accessibility for small civil practices, an interface explicitly designed for attorney interaction (not just examiner use), and case packet export quality optimized for court filing rather than eDiscovery handoff.
Whether it achieves those differentiators is a judgment call each practitioner has to make based on their specific workflow and case types. I think it does — but I acknowledge that I’m not a neutral evaluator.
FAQ
Who should use ExtractPhone?
Civil forensic practitioners who do their extractions with standard forensic tools and need a better way to organize, review, and present that evidence to attorneys and courts. It’s particularly useful for solo examiners and small practices where the extraction-to-report workflow is currently manual and time-consuming.
Does ExtractPhone work with law enforcement cases?
ExtractPhone’s features apply to law enforcement use cases too, but the product is optimized for civil forensic workflows. Law enforcement agencies with existing case management systems and dedicated review platforms may find ExtractPhone redundant. For LE examiners who work civil litigation support, the value is clearer.
How does ExtractPhone handle data security and client confidentiality?
Case data in ExtractPhone is handled with standard digital evidence security practices. Data is not shared with third parties. For specific security questions related to your jurisdiction’s requirements for client confidentiality, contact us directly — we can walk through the technical architecture. This is something we take seriously, and detailed documentation is available.
What’s the best way to evaluate ExtractPhone before committing?
Use it on a real case — specifically a case where the extraction is already complete and you’re trying to organize it for attorney review. That’s the context where the value either is or isn’t apparent. A demo on a sample dataset will show you the interface; a real case will show you whether it fits your workflow.
Final Assessment
I built ExtractPhone to solve a real problem in my own practice. It does solve that problem — the presentation and organization gap between forensic extraction tools and attorney-ready evidence is real, and ExtractPhone addresses it better than patching together PDF exports and email threads.
It’s not complete. No software product at this stage is. The import compatibility gaps are real. The search needs to get more sophisticated. Performance on large cases needs improvement.
But the core — communication timeline, media gallery, case packet export, attorney-facing interface — works. It saves real time on civil forensic cases. The practitioners I’ve walked through it consistently find something useful in it.
Because I built it, you should weight my assessment accordingly. The best thing I can offer you is the honest framing I’ve tried to give here: here’s what it does, here’s where it falls short, here’s the conflict of interest. Judge for yourself at [extractphone.com](https://extractphone.com).
Derick Downs is the founder of Octo Digital Forensics and the parent organization of Digital Forensics Today. He has conducted mobile device forensic examinations in civil and criminal matters for 20+ years and holds Cellebrite CCPA and CCFE certifications.
