Build a self-contained HTML folder explorer from a PC3000 recovery CSV or an .acerep file-selection report — open offline or share.
Ever have a data recovery case where you are part way through a very tough job, imaging with Data Extractor, and want to give your customer an easy-to-view HTML report of which files have been successfully imaged and which are still bad due to unread or damaged sectors?
It is for that reason that we developed this. Have fun!
Need the customer to choose which files and folders to recover from a Data Extractor snapshot — without giving them PC3000 — then bring that selection back as a .roa Import report?
Import the .acerep, brand an HTML picker, let them select, and export a .roa for Data Extractor.
Build an offline HTML sector map (LBA 0 at top-left) from a Data Extractor Attr.map. Toggle the full DE legend or a simple Good / Bad / Unread view.
Optionally add Head.map (filter by head) and task.info (patient model & S/N).
Have an R-Studio (or DeepSpar) HTML recovery list and want the same offline good/bad folder explorer we build from a PC3000 CSV?
Drop the R-Studio report HTML here — we convert it as best we can into that status report format.
Saved recovered files into Good and Damaged folders on the destination drive? Build the same color-coded status report from a DOS dir /a /s listing — merged back into the original tree.
After import, pick Good/Damaged folders when they exist — or treat the whole listing as all good, all damaged, or all unknown. Nested bad-inside-good (or the reverse) is detected automatically.
Have a UFS Explorer HTML scan report? Convert it into the same offline good/bad folder explorer — and drop the damaged-objects text report when you have it.
Without a damage report, choose to treat every file as good or as unverified.
Have a Snap2HTML report of a volume or recovered tree and want it in the same branded explorer as our other reports?
Drop the Snap2HTML HTML here — we import the folder tree as a directory snapshot (no good/bad coloring).
We generate customer-facing HTML recovery reports (status, file selection, sector maps, and more). Those reports can show your company name, logo, colors, and contact details.
Fill in the form below, download the JSON file, and email it back to us. Nothing is uploaded from this page.
.json file (it includes the logo).Keep a copy of the JSON. If you change your logo or colors later, send an updated file.
The export is semicolon-delimited and includes size, dates, absent sectors, and problem sectors. If Map statistics are omitted, every file is listed as unverified.
.html file in any browser — no internet or this site required.Chinese / Japanese / Korean names need a Unicode-preserving source. PC3000 CSV on a Western Windows code page often replaces them with ???? before this tool ever sees the file. Prefer UTF-8/Unicode CSV, an .acerep, or a UFS / R-Studio HTML report.
* and ? wildcards) and the scope dropdown to limit results..acerep..acerep onto the box below (or click to browse).Plain SQLite and zlib-compressed .acerep files are both supported. Nothing is uploaded — files stay in the browser.
Attr.map (required). Optionally drop Head.map and/or task.info with it, or one file at a time.Bad includes ECC, no-CRC, invalid, read errors, and readiness loss. task.info supplies patient model & S/N.
.html file onto the box below (or click to browse)..txt — no need for Mark Files in the source HTML).This is a best-effort conversion of R-Studio’s embedded file tree. Symlink-style entries without content are skipped. R-Studio does not expose PC3000 “absent sectors” the same way.
dir /a /s > report.txt..txt here. If Good/Damaged folders are present, pick them (guesses fill in when names look familiar). If not, treat the whole listing as All good, All damaged, or All unknown.If Bad is inside Good (or the reverse), the more specific path wins. Works with English and common localized dir headers.
.html (required). Drop the damage .txt with it or afterward..xsdf). If no damage report is provided, choose All good or All unverified, then preview or download.Bad files are matched by UFS object ID from the damage report. The HTML tree alone has no good/bad flags.
.html file onto the box below (or click to browse). You can drop it on any mode — Snap2HTML is detected automatically.This imports Snap2HTML’s dirs[] tree. It is not a PC3000 status report — files are not marked good or bad.
Required for each report. Cleared after generate so the next job gets a fresh name.
If the listing has Good and Damaged folders, pick them below. Otherwise treat every file as good, damaged, or unknown.
No damaged-objects file loaded. Choose how to treat all files:
When the customer clicks Email Selection, this address is used as To: and the selection file is attached (via a downloadable .eml).
Use line breaks for street / city lines — they show separately from phone, email, and website.
Quick presets — or use the color wheel below for any brand color.
Save your logo, colors, and contact details to reuse on another computer.
Loading usage stats…