Recovery instructions, downloads and FAQs
Download Sony XAVC Recovery, make a full-sector card image, and follow the correct workflow for your computer.
Choose your platform.
The Windows and Mac builds use different workflows. Pick the platform you are using and only those instructions will be shown.
Stop using the card and make a full-sector image first. Every new photo or recording can overwrite the video you want back. Sony XAVC Recovery works against the image, not the original media.
Now available natively for Apple Silicon Macs.
Choose or drag a .img, .dd or .dsk full-sector image into the app. Sony XAVC Recovery analyzes the image and recovers the detected recordings automatically.
Recovered files are written beside the source image in an _Recovered folder.
Drop the image and let it run
Drag the full-sector image onto the window or choose it manually. Progress is shown while the source is scanned, recordings are identified and recovered files are written.
Use Show Output when recovery finishes to open the recovered-files location. No folder scavenger hunt required.
Analysis and recovery stay local
The source image is opened read-only. The activity area shows scan and recording progress while the recovery engine works from the local image.
Analyze first, then choose what to recover.
The Windows build gives you manual analysis, recording review and selected recovery. Follow the four steps below.
Windows screenshots are from Version 2.2.28 using a 256 GB Sony card (238.475 GiB image). Counts vary by card.
Select the image and where recovered files should go
Source image. Click Open… and select the full-sector .img, .dd or .dsk image of the card.
Output folder. Choose where reconstructed MP4 files will be written. Allow enough free space for the footage you expect to recover.
Once both paths are set, Analyze becomes available. Recover Selected and Recover All stay disabled until the source has been analyzed.
Run Analyze and watch the card map fill in
The first pass reads the full source image. The sector map fills as the engine finds readable areas, Sony KKAD bookkeeping and MOOV structures.
Analysis then validates the recording relationships it found. The four-stage rail keeps the workflow visible: 01 ANALYZE, 02 PROCESS, 03 VERIFY, 04 RECOVER.
Recovery remains unavailable until analysis has finished. The source image stays read-only throughout.
See what is recoverable before writing anything
The completed list shows each recording's filename, date, codec, resolution, duration, size and status. Recoverable means the engine accepted the reconstruction. Review marks a result that needs attention rather than silently treating it as certain.
The summary separates recording results from lower-level recovery readiness. In this example, 455 recordings are recoverable and 6 require review.
Check the recordings you want, or use Recover All. The Space bar can toggle the selected recording's checkbox.
Recover the recordings you want
Recover Selected writes only the checked recordings. Recover All writes the full accepted set.
The lower progress bars separate queue progress from the recording currently being written. The status line reports the active file and percentage.
Show frame preview while recovering is optional and off by default. Enabling it can significantly slow recovery, especially with large or high-resolution recordings. Useful when you want it; expensive when you do not.
Activity shows the detailed work
Open Activity when you want the technician view. It is not required for normal recovery.
The window exposes structure scans, mapping decisions, source identity, recording geometry and rebuild stages as they happen.
If a card behaves differently from the expected Sony layout, this is the first place to look.
Use the Hex Viewer to see what the image is actually returning
The Hex Viewer is read-only. It lets you jump to an offset or sector, move sector by sector, and search the source image for text such as kkad.
If Analyze finds nothing, inspect several widely separated areas. Large zero-filled regions can help determine whether the host is seeing useful card data or an empty/unmapped logical view.
That alone does not prove CMD38 or physical NAND erase. A controller can return zeros after changing its logical mapping even while older data may remain in flash.
Something is off.
The common failures and the first thing to check.
You formatted in camera and got nothing at all
See SD erase in Sony cameras for the CMD38, controller-mapping and raw-flash explanation.
Ambiguous mappings is not zero
More than one physical location satisfied the available evidence, so the program did not classify the mapping as proven. A Review recovery may still be attempted in some cases, but a file that happens to play does not by itself prove that the ambiguous physical mapping was correct. The FAQ explains why the uniqueness requirement matters.
It ran out of disk space partway
You're writing full bitrate video back out, so a nearly full 128 GB card needs close to 128 GB somewhere to land. Point the Output folder at a bigger drive and run it again. Nothing got hurt, and the cached scan means the second run goes straight to writing.
It is taking forever
The first pass must read the entire image, so storage speed wins. Put a 128 GB image on USB 2.0 and the software gets to enjoy 2008 with you. Copy it to a local SSD and run it again.
The sample clip won't play
Try VLC first. Windows' built-in player is picky and occasionally rejects files VLC plays fine. If VLC also refuses it, send the Activity window and analysis numbers to info@icubedev.com. Failed cards are useful. They show what the tool missed.
Picture is right, audio is off
Audio comes from the card's own extents where they survived, with tighter fallback rules where they didn't. On a heavily reused card that fallback occasionally lands wrong. The picture is still good. Let us know and include the clip number.
Still stuck
Email info@icubedev.com or call (888) 728-CUBE. It is a free tool, so replies may not be instant, but failed cards are useful. They show where the assumptions break.
SD erase in Sony cameras, and why the card can read as truly empty
If software sees an apparently empty card, the question is whether the filesystem was reset, the card controller discarded its map, or the flash itself was actually erased.
The camera asks. The card decides.
A memory card, whether SD, microSD or CFexpress, has its own controller, firmware and private map between the sectors the camera sees and the NAND flash underneath. The camera asks the card to format, write or erase; the controller decides how that request is carried out.
Rewriting the index versus asking the card to erase
“Format” can mean rewriting the filesystem index or asking the card to erase. Some Sony cameras may issue CMD38, but CMD38 is still a request: the controller may drop mappings, defer cleanup or erase blocks. The menu label alone does not prove what happened to the NAND.
I have also seen recoverable in-camera formats, including cases on Lexar Professional 1066x media, where the recording data remained readable after formatting. That observation is useful, but it is not a promise about another card or firmware revision.
The read-only Hex Viewer gives you a quick host-side check. If widely separated sectors are returning nothing but 00, the image is effectively blank to normal software. That can support an erase or mapping-loss diagnosis, but the byte pattern alone cannot tell you what the controller did internally.
Even so, empty does not always mean erased
The controller can lose the logical map while the physical flash still contains data. To normal software that card may look empty because the old sectors are no longer addressable through the card interface.
When that happens, recovery moves from software to raw-flash work: read the memory directly, rebuild the controller mapping, then reconstruct the Sony recordings from the resulting image.
Data that still exists but can't be addressed can sometimes be recovered, by reading the flash chips directly and rebuilding the card's map from scratch. Data whose flash blocks have actually been reset cannot be recovered by anyone, with any equipment, at any price. Rebuilding the map tells you where something was. It cannot bring back something that isn't there.
Run the free tool first. If a lab quotes raw-flash work, ask whether your controller is supported and what happens if the flash blocks have already been erased.
Other video recovery utility
Not part of Sony XAVC Recovery. This separate Windows tool uses a different recovery method and is not needed to operate Sony XAVC Recovery.
iCube Advanced Video Carver
Recover deleted MP4, MOV and other video recordings using FAT, exFAT and NTFS filesystem records where available, or raw video carving when those records are missing. Filesystem-assisted recovery can preserve original filenames and follow fragmented files. Unfortunately, a file extension is not a magic repair button.
Video formats: .mp4, .mov, .m4v, .3gp, .3g2, .mts, .m2ts, .ts, .mpg, .mpeg, .vob, .avi, .dv, .mod and .tod.
Different job, different method. Advanced Video Carver can use surviving FAT, exFAT and NTFS records to recover files with their original filenames, follow fragmented file allocations, and rejoin fragmented MP4 recordings. It also carves recognizable video data when filesystem records cannot help. Sony XAVC Recovery instead rebuilds supported Sony XAVC recordings from Sony-specific recording structures. Neither tool can restore bytes that have been overwritten or erased. See the FAQ comparison.
Questions people actually ask
Short answers first. The technical rabbit holes are linked when they are actually useful.
What is iCube Advanced Video Carver, and how is it different from Sony XAVC Recovery?
Advanced Video Carver searches for recognizable video formats including .mp4, .mov, .m4v, .3gp, .3g2, .mts, .m2ts, .ts, .tod, .mpg, .mpeg, .vob, .mod, .avi and .dv. It can also use FAT, exFAT and NTFS filesystem records to recover original filenames and follow fragmented files. A recognized signature alone does not guarantee a complete recording.
iCube Advanced Video Carver 2.7.7 is a Windows video recovery utility combining filesystem-assisted recovery with raw carving. Where FAT, exFAT or NTFS records survive, it can recover original filenames and fragmented file allocations. It can also rejoin fragmented MP4 recordings. When filesystem information is unavailable, it searches the source for recognizable video structures.
Sony XAVC Recovery 2.2.28 uses Sony-specific recording metadata and sample tables to reconstruct supported XAVC MP4 recordings. Its structural reconstruction and mapping checks differ from Advanced Video Carver's filesystem-assisted and general video recovery methods.
Use Advanced Video Carver to recover deleted video from surviving filesystem records, including original names and fragmented files, or to scan for video when directory records are gone. Use Sony XAVC Recovery for Sony XAVC recordings requiring Sony-specific reconstruction. Neither tool can recover overwritten or physically erased bytes. Download Advanced Video Carver 2.7.7.
Can Advanced Video Carver recover fragmented video?
Yes. Version 2.7.7 uses surviving FAT, exFAT and NTFS filesystem records to follow fragmented file allocations and can rejoin fragmented MP4 recordings. When those records are missing, raw carving may still locate video, but reliable recovery of scattered pieces becomes harder. Sony XAVC Recovery uses a separate Sony-specific method for supported XAVC recordings.
How do I make an image of my Sony SD card or CFexpress card?
There are many free disk-imaging tools and step-by-step guides available for Windows and macOS. Search Google for how to create a full-sector image of an SD card or CFexpress card and use a tool you are comfortable with. The important part for Sony XAVC Recovery is that you image the entire physical card, not just a partition or mounted volume.
Why do I need to make an image instead of recovering directly from the card?
Because recovery is much less exciting when the source stops changing underneath you. A fixed copy is the safer target. The program reads the image without writing to it, and you can analyze it again without repeatedly touching the original card. The card gets one job: give us the best copy of its sectors it can.
Why is Sony XAVC Recovery free?
Because the software grew out of real Sony recovery cases and the reverse-engineering work needed to solve them. Publishing the tool also gives unusual cards a chance to expose layouts we have not seen yet. iCube Development does paid data recovery work, but the software itself is free. No licence key, subscription or paid unlock.
Does Sony XAVC Recovery upload my video or card image?
No. Analysis and recovery run on your computer. The recovery program does not upload your card image or recovered video to iCube Development.
Does this software recover recordings from GoPro, Nikon or Canon cameras?
No. Sony XAVC Recovery is built specifically around Sony XAVC recording structures. For GoPro, Nikon, Canon and other camera formats, search Google for recovery software for that camera or recording format. There are plenty of free recovery tools for other camera formats. Use one built for that job rather than asking a Sony-specific tool to pretend.
Will it work with my Sony camera?
The tool does not use a camera-model whitelist. It looks for supported Sony XAVC recording structures in the card image. That means a body does not have to appear on a compatibility list to work, but the recording still needs to use a supported Sony XAVC MP4 layout.
Does it work with SD, microSD and CFexpress cards?
Yes, provided you can make a readable full-sector image and the card contains a supported Sony XAVC MP4 recording layout. The recovery logic cares about the surviving recording structures, not the logo printed on the memory card.
Can Sony video still be recovered after the card was formatted?
Sometimes. A format can remove filesystem bookkeeping while leaving recording data behind, but an in-camera erase may also cause the card controller to unmap or erase blocks. The menu option alone does not tell you which happened. See Deleted or formatted?
Why is my 256 GB card image only about 238 GiB?
That is normal. Card manufacturers advertise capacity in decimal gigabytes, while many operating systems and recovery tools display binary gibibytes. A nominal 256 GB card is roughly 238 GiB. Nothing went missing in the conversion.
What does a .partial.mp4 file mean?
It means the program could prove and preserve a usable portion of the recording, but a later video or audio extent could not be established safely. Rather than invent the missing part or throw away everything, Version 2.2 can keep the proven portion as .partial.mp4.
How do I create a diagnostic bundle, and what is it for?
A diagnostic bundle is the best thing to create when the program finds the wrong number of recordings, finds nothing useful, marks unexpected items for review, produces a file that does not play correctly, or encounters a Sony layout it does not yet understand.
How to create one: select the source image as you normally would and reproduce the problem first. Then choose File > Create Diag. Bundle.... If you are testing an unformatted reference image, add that reference before creating the bundle so its characterization is recorded too.
The bundle records the program version, source identity, analysis results, Sony structures found, mapping and reconstruction decisions, recovery traces and other technical details needed to understand what the engine did. If a reference image is attached, its characterization and identity are recorded as well. The full card image and recovered videos are not placed in the diagnostic bundle.
The point is not simply to collect a log. The bundle lets iCube Development compare what the program expected with what was actually present on that card, which is how unsupported layouts and incorrect reconstruction assumptions can be isolated without guessing.
What is Extended Translation Recovery, and when should I enable it?
Extended Translation Recovery is an optional recovery path for cards whose reported sector addresses may not match where the useful data is really coming from. This can happen with damaged, counterfeit, fake-capacity or failing flash media. A card can appear readable while returning repeated, wrapped, shifted or otherwise abnormal data for parts of its address range.
Enable it with Advanced > Enable Extended Translation Recovery. It is normally left off because a healthy card image should not need alternate address translations. When enabled, the program tests additional translation possibilities and still requires the resulting Sony recording structure to satisfy the normal recovery checks. It does not simply accept more matches because they happen to contain video.
Use it when the normal analysis looks internally inconsistent, the sector map suggests repeated or strangely displaced data, the card reported a suspicious capacity, or the media is known to be counterfeit or failing. It can take longer because the program has more candidate mappings to test. It does not repair erased flash and cannot recover sectors that the card never returned in the image.
What does Add an unformatted reference image do?
This is optional and is mainly for a Sony recording layout the program does not yet understand well enough from the damaged image alone. Choose File > Add Unformatted Image... and select a full-sector image of a healthy, unformatted Sony card that represents the same recording setup as closely as possible.
The best reference is from the same camera model and recording mode, including the same codec family, resolution, frame rate and related recording settings. It does not need to contain the missing footage. Its job is to provide a known-good example of how that Sony setup writes its recording structures and transitions to the card.
The reference is opened read-only and is used for comparison. Its video is not mixed into the damaged card's recovery and it cannot replace missing source bytes. When a diagnostic bundle is created, the tool can record the reference image's characterization and identity without placing the reference image itself in the bundle.
You do not need a reference image for a normal supported recovery. Add one when analysis suggests an unknown or unfamiliar layout, or when iCube Development asks for one while investigating a diagnostic bundle.
What does Recover fragmented AVC transitions do?
This option is for AVC/H.264 recordings that change from one physical region of the card to another and cannot be completed by the normal direct mapping path. A recording may be logically continuous even though its next group of frames is physically far away on the card.
When enabled, Sony XAVC Recovery follows the surviving Sony and MP4 structure across the break, calculates what the next AVC samples must look like, searches for a physical location that satisfies that structure, and accepts the transition only when there is a unique physical match. It then checks the rebuilt transition by decoding it in context with the surrounding video.
This is not blind fragment scanning and it does not accept a candidate merely because it contains valid H.264 data or produces a playable picture. If more than one physical location fits, the transition is not treated as proven. The option is therefore useful for difficult fragmented AVC cards, but it should not be enabled simply to make the program return more footage.
It applies to AVC/H.264. HEVC/H.265 uses its own reconstruction paths.
How is Sony XAVC Recovery different from Disk Drill?
Disk Drill and Sony XAVC Recovery can both use camera-aware information to recover video that ordinary file carving misses, but they are built around different goals.
Disk Drill's Advanced Camera Recovery is a broader recovery product. Its Sony-aware recovery can locate camera metadata and matching video fragments across a card and reconstruct footage that a normal contiguous scan may miss. That broader approach can return more candidate footage on some cards.
Sony XAVC Recovery is narrower and deliberately conservative. It is built specifically around supported Sony XAVC MP4 structures. A fragment is not accepted merely because it looks like the right codec, is near the expected location, fits one boundary, or produces video that plays. The engine checks the surviving Sony metadata, the recording's expected sample sizes and order, the physical layout, and whether exactly one physical location satisfies those constraints. The reconstructed result is then decoder-checked in context.
The practical difference is the acceptance standard. If two physical locations can satisfy the available evidence, Sony XAVC Recovery does not silently choose one. The mapping remains unresolved or is marked for review. This can mean another recovery program returns more footage while Sony XAVC Recovery returns less, because this tool prefers to leave a fragment unresolved rather than guess which copy belongs to the recording.
When Sony XAVC Recovery reports a recording as fully recovered, it is not creating replacement video. It does not transcode the recording, interpolate missing frames, synthesize audio, conceal bad sections or make a damaged stream look playable. The accepted video and audio samples are copied from the source image using the original bytes, exact sample sizes and proven playback order.
That distinction matters. A successfully reconstructed recording contains the original Sony picture and sound data, not an approximation of it. The recovery process does not intentionally drop frames, substitute audio or re-encode the media. If the engine cannot prove a required piece of the recording, it does not manufacture one. The recording is instead left unresolved, marked for review, or, where possible, the proven portion is preserved as a .partial.mp4.
The finished MP4 container may contain structures rebuilt by Sony XAVC Recovery, so the recovered MP4 file itself should not be described as a byte-for-byte copy of the deleted MP4 file. The important part is that the recovered media payload is source-backed original data rather than regenerated video.
A file merely playing successfully is therefore not treated as proof. Sony XAVC Recovery writes its physical mapping decisions to the recovery report so you can see where the accepted pieces came from and why they were accepted.
And one other difference is unusually simple: Sony XAVC Recovery is free. No licence, subscription, upgrade screen, or “great news, we found your wedding video, now enter your credit card” moment.
There is no reason you cannot run both programs against the same read-only card image and compare the results. Disk Drill is useful when broad camera-aware recovery is the priority. Sony XAVC Recovery is useful when you want Sony-specific reconstruction where every accepted piece must trace back to the original card data and satisfy a strict uniqueness requirement. See the recovery-method comparison and five proof gates.
Why can normal recovery software find video pieces but still produce broken MP4 files?
Finding Sony video bytes is only part of the problem. A recording can be split across the card, and the pieces still need the correct sizes, order, timing and association. Sony XAVC Recovery uses surviving Sony recording structures to prove how those pieces fit back together. The boxes-and-packing-list explanation shows why.
Is this a general broken-MP4 repair tool?
No. It is designed to reconstruct supported Sony XAVC recordings from a full-sector card image. If you already have an ordinary damaged MP4 file and no card image, this is probably the wrong tool.
What if the program finds nothing useful?
It can mean the recording data was overwritten, the controller is returning an empty or unmapped view, the flash was actually erased, or the surviving Sony layout is not supported yet. Those are very different problems. The read-only Hex Viewer and diagnostic bundle can help separate them. See the SD erase explanation.
Can I use it commercially?
Yes. The tool is free to use on your own recovery work or client recovery work.
What if the card is physically damaged or cannot be imaged?
This tool needs a readable full-sector image. If the card is hot, unstable, showing the wrong capacity or producing repeated I/O errors, stop and address the hardware problem first. Software cannot reconstruct sectors the computer cannot read.