SUBMIT A FILE TYPE CONTACT US SUPPORT ABOUT US

What Is a RAR File? The Archive With Its Own Checksums, and How to Check and Repair One

A RAR file is an archive that packs files into one and checks every part with a CRC32. Four readers agreed on only 10 of the 21 damaged copies we made of one. Jump to your question below, or work through it in order.

41 min read Updated October 2026 Checked against sources and tests

What Is a RAR File? An archive that packs files together, from 1993

Short answer

A RAR file is a compressed archive that packs files and folders into one file. It is a closed format made by Eugene Roshal, and the name means Roshal Archive. Wikipedia dates the first release to March 1993, and RAR5 came with WinRAR 5.0 in April 2013.

We tested 281 public RAR files with four readers, unrar, 7-Zip, bsdtar and unar. All four passed 74 of them. We then damaged one RAR file in 21 ways, and the four readers agreed on only 10 of those copies.

To open one, read the open steps. To check one, read the check steps. If your RAR file will not open, begin with the eight causes.

A RAR file is an archive. It packs files and folders into one smaller file, and it checks itself with a CRC32 on every header and every file. Windows 11 24H2 opens one without extra software, per Microsoft.

Picture an email attachment called photos.rar. You double click it and nothing opens on an older PC, because RAR is not built into every system. Picture a second file, backup.part2.rar, that is only a piece of a set. Both end in .rar, and only the bytes inside show what you have.

Wikipedia describes RAR as a format made by the Russian engineer Eugene Roshal, with a first release in March 1993. The copyright holder is his brother Alexander Roshal. The name stands for Roshal Archive, and the compression is proprietary.

RARLAB gives away the code to unpack RAR files and keeps the code to pack them. The Wikipedia page says the licence allows software that unpacks and forbids software that creates RAR files. That is why free tools read RAR files and few of them write one.

The format has two main eras. RAR 1.5 to 4 files start with a 7 byte signature, and RAR5 files start with 8 bytes. Wikipedia says RAR5 came with WinRAR 5.0 in April 2013 and brought AES 256 encryption, an optional BLAKE2 file hash, UTF 8 names and dictionaries up to 1 GB.

IANA registered application/vnd.rar on 2016-07-14 with the extension .rar and the magic number 52 61 72 21 1A 07 00. That is the older signature. The record also says security issues for the type have not been assessed.

Where our RAR files come from

We read 281 files from three public projects. They are libarchive with 116 files, junrar with 115 and rarfile with 50. We dropped 4 files that were exact copies of others. All 281 end in .rar.

They are test files, and many are made to break readers on purpose. They are 7 to 1,081,705 bytes long and 7,146,553 bytes in total, and the median is 508 bytes. 7-Zip listed 690 entries in the files it could open, and the largest has 46.

So this page studies how readers treat the RAR layout, and not a sample of RAR files from everyday inboxes. We made one archive of 5 files with RAR 7.00 and damaged it in 21 ways. We opened nothing on Windows or macOS, and we tested no password that opens.

RAR file facts at a glance

Quick facts about RAR files
Property Value
Meaning An archive format. It stores files, their names and sizes, and compresses the data.
Ending .rar. Wikipedia also names .rev for recovery volumes and .r00, .r01 and so on for older split sets.
Maker Eugene Roshal. The first release was in March 1993, per Wikipedia.
First bytes Rar! then 1A 07 01 00 in 129 of our 281 files, and 1A 07 00 in 144. IANA lists the older one.
Layout A signature, a main header, then a header and packed data for every file, and an end block.
Checksums A CRC32 on every header and on every file. RAR5 can use a BLAKE2 hash instead of the file CRC32.
Encryption AES. Wikipedia says RAR5 uses AES 256. Microsoft says Windows 11 24H2 does not open encrypted archives.
Repair A recovery record inside the file and recovery volumes in .rev files, per Wikipedia.
Our tests 281 files, 21 damaged copies, 4 readers, 2 repair routes and a script of 36 lines.

Wrong page? A ZIP file is another archive format. See how ZIP, 7Z and TAR files differ.

Which Kind of RAR File Do You Have? Four starts, and the first bytes name the kind

Four starts name the kind of a RAR file. In our 281 files, 129 start with the RAR5 signature, 144 with the older one, 7 with RE~^ and 1 with something else. The ending names none of them.

Read the first bytes and follow the figure. We tested all four starts with four readers. The ending is no help, because all 281 files end in .rar and they are not all the same kind.

Decision chart with four ways a RAR file can start, the RAR5 signature, the older RAR 1.5 to 4 signature, the RAR 1.4 marker and anything else, with how many of our 281 test files start that way and how many of those files every one of four readers passed.
Figure 1. Four ways a RAR file can start in our 281 test files.

The four starts in detail

Four starts of RAR files and how four readers handled them
Start Files and results
Rar! 1A 07 01 00 129 files. This is RAR5. unrar passed 57, 7-Zip 47, bsdtar 77 and unar 78. All four passed 41.
Rar! 1A 07 00 144 files. This is RAR 1.5 to 4. unrar passed 58, 7-Zip 58, bsdtar 42 and unar 71. All four passed 33.
RE~^ 7 files. The file command calls them RAR archive data older than version 1.5. Only unrar passed one of them.
Anything else 1 file. The file command printed data. No reader passed it.

Start with the first bytes

Open the RAR file in a hex viewer, or use xxd -l 32 example.rar on Linux or Mac. A RAR5 file starts with 5261 7221 1a07 0100. Those are the letters Rar, an exclamation mark and four control bytes. RARLAB says RAR5 uses an 8 byte marker.

The first bytes and the type of one RAR file
xxd -l 32 example.rar
00000000: 5261 7221 1a07 0100 f3e1 82eb 0b01 0507  Rar!............
00000010: 0006 0101 8080 8000 2b2b 3884 1e02 02dc  ........++8.....
file -b example.rar | cut -d, -f1-2
RAR archive data, v5
file -b --mime-type example.rar
application/x-rar

The file command reads the contents, not the ending. It named 273 of our 281 files RAR archive data, 7 more RAR archive data with a version below 1.5, and 1 with the bare word data. It named all 129 RAR5 files version 5.

The signature can come after other bytes. RARLAB says readers search from the start of the file up to the biggest self extracting module. We tested what that means, and the damaged copies show it, because four junk bytes in front stopped all four readers.

First bytes first Rar! plus 1A 07 01 00 is RAR5. The older kind ends in 07 00.
Old files are rare Only 7 of our 281 files use the RAR 1.4 marker, and one reader passed one of them.
The ending last All 281 files end in .rar, and the layout inside is not the same.
Pieces are not archives A split set needs every part. Alone, none of 66 parts passed in unrar or 7-Zip.

Not sure your RAR file is a RAR file at all? Check it with our script.

What Is Inside a RAR File? Blocks in a row, and every block has a CRC32

A RAR5 file is blocks in a row. A signature comes first, then a main header, then a header and packed data for every file, then an end block. Our example RAR file is 3,160 bytes long and stores 5 files that add up to 11,508 bytes.

We looked inside a RAR file because its layout explains every result later on this page. We made example.rar with RAR 7.00 from five files, readme.txt, sales.csv, config.json, notes.md and blob.bin. The listing shows what a reader sees first.

The listing and a test of one RAR file
unrar l example.rar
Archive: example.rar
Details: RAR 5

 Attributes      Size     Date    Time   Name
----------- ---------  ---------- -----  ----
 -rw-r--r--      1500  2026-10-31 06:07  blob.bin
 -rw-r--r--      2664  2026-10-31 06:07  config.json
 -rw-r--r--      1898  2026-10-31 06:07  notes.md
 -rw-r--r--      3393  2026-10-31 06:07  readme.txt
 -rw-r--r--      2053  2026-10-31 06:07  sales.csv
----------- ---------  ---------- -----  ----
                11508                    5
unrar t example.rar
Testing archive example.rar
Testing  blob.bin  OK
Testing  config.json  OK
Testing  notes.md  OK
Testing  readme.txt  OK
Testing  sales.csv  OK
All OK

The five files add up to 11,508 bytes, and the packed data takes 2,947 of the 3,160 bytes. blob.bin is stored with method m0, so it keeps its 1,500 bytes. The other four use method m3 and shrink to between 6 and 42 percent of their size.

RAR 7.00 on Linux rejected the option -ma4 with an error, so every RAR file we made is RAR5. The RAR 1.5 to 4 files in this study come from the three test projects.

Diagram of one RAR5 file of 3,160 bytes in four blocks: the 8 byte signature, a main header, five file blocks that all store a header and the packed data, and an end block of 8 bytes, with three rules about header checksums, how readers find the signature and what a recovery record does.
Figure 2. One RAR5 file from our tests, example.rar. The blocks are not drawn to scale.

The blocks, one by one

RARLAB says every block starts with a CRC32 of the block. A size field follows, then the block type and flags. Sizes use a variable length number, where every byte stores 7 bits and the high bit says that another byte follows.

In our example the signature takes bytes 0 to 7 and the main header takes 16 bytes. The first file block starts at byte 24 and stores the header for blob.bin and its 1,500 bytes. The last block is 8 bytes, the end block.

RARLAB lists five block types. Type 1 is the main archive header and 2 is a file header. Type 3 is a service header, 4 is the archive encryption header and 5 is the end block. Our example has types 1, 2 and 5. A file with a recovery record adds type 3.

What every part stores

Parts of RAR files and what we saw
Part What it stores
Signature Eight bytes in RAR5, Rar! then 1A 07 01 00. The older kind has 7 bytes and ends in 00.
Main header Type 1. Its flags say if the archive is split, solid, has a recovery record or is locked. In our example it is 16 bytes.
File header and data Type 2. It stores the name, both sizes, the time, the CRC32 of the data and the method. The packed bytes follow it.
Service header Type 3. RARLAB says a recovery record is stored as a service header named RR, before the end block.
Encryption header Type 4. It appears when the headers are encrypted, and then every later header begins with an IV.
End block Type 5. In our example it is 8 bytes and closes the file.
CRC32 A checksum of every header and, in file headers, of the unpacked data. Our readers refused most copies with a bad CRC32.
Variable length numbers Sizes use 7 bits per byte. A header size of 3 takes one byte and a size past 127 takes two.

What the sources say

RARLAB publishes the RAR 5.0 format notes on its technote page. They give the marker, the five block types, the header CRC32 and the variable length numbers. They do not describe the inner structure of the recovery record, so we only tested what it does.

Wikipedia says RAR 3 combines Lempel Ziv compression with PPM, and that recovery records came in RAR 2.0 and recovery volumes in RAR 2.9. We did not read the compressed streams, so we make no claim about the methods inside our files beyond what unrar printed.

The map is small. Our script reads the signature, every header CRC32, the end block and the data CRC32 of stored files. It cannot check packed data, so a changed byte inside a packed file can pass it, as the 21 copies show.

What Did We Find in 281 Test RAR Files? Four readers, and they did not agree

We read 281 public test files with four readers and a 36 line script. unrar passed 116, 7-Zip 105, bsdtar 119 and unar 149. All four passed 74 files, and none passed 105.

All 281 files come from three public test sets, so this is a study of those projects and not of RAR files in general. Many files exist to break readers, and a refusal on them is the right answer. We used the layout, because every file claims to be a RAR file.

Readers were unrar 7.00 from RARLAB, 7-Zip 23.01, bsdtar 3.7.2 with libarchive 3.7.2 and unar 1.10.1, all on Linux. A reader passed a file when its test or extract command exited with 0. We gave no password, and we tested every file alone in its own folder.

281 files read
4 readers on every file
21 damaged copies of one file
13 copies our script flagged or warned on
Bar chart of 281 public test RAR files by size, from 7 bytes to 1,081,705, next to the number of files every one of four readers passed, a grid of results by kind of file, and four measured facts.
Figure 3. 281 files, four readers and four measured facts.
What six checks found in 281 files
Test Result
The file command Named 273 files RAR archive data, 7 RAR archive data older than version 1.5 and 1 data.
unrar 7.00 Passed 116 files and refused 165. It passed 4 files that no other reader passed.
7-Zip 23.01 Passed 105 files and refused 176. It passed 2 files alone and crashed with a segmentation fault on 13.
bsdtar 3.7.2 Passed 119 files and refused 162. It passed 12 files alone and timed out on 2 after 30 seconds.
unar 1.10.1 Passed 149 files and refused 132. It passed 22 files alone and crashed on 1.
Our script Printed OK for 242 files and FLAG for 39. 144 of the OK files are the older kind, where it checks only the signature.
Sizes 7 to 1,081,705 bytes, with a median of 508 and a total of 7,146,553. 93 files are under 200 bytes.
Entries 690 entries in the files 7-Zip could list, and 46 in the largest.

One layout and four starts

129 files start with the RAR5 signature and 144 with the older one. The four starts split the files into 129, 144, 7 and 1, and the start predicts how readers do. All four readers passed 41 RAR5 files and 33 older ones, and none of the 8 files with another start.

The 20 password protected files, 12 older and 8 RAR5, failed almost everywhere. unrar passed 1, unar 1, bsdtar 2 and 7-Zip none. 21 files are solid. We gave no password, so this shows that a password is needed and not how readers treat a wrong one.

Where the four readers split

The four readers gave one answer on 179 files. They all passed 74 and all refused 105. They split on the other 102. unar passed the most files, 149, and it passed 22 files that no other reader passed.

bsdtar passed 12 files alone, unrar 4 and 7-Zip 2. Many of the bsdtar cases are pieces of split sets. bsdtar passed 25 of the 66 volume parts alone, unar passed 22, and unrar and 7-Zip passed none.

Volume parts need their neighbors. In a first test, with all files in one folder, unrar passed 63 of the 66 parts, unar 60 and 7-Zip 14. Alone, the same parts failed. Keep every part of a split set in one folder, and start with the first.

That first test showed a second trap. In our damaged test, unar returned all 5 files from a 24 byte copy when other files sat beside it, and returned none when it was alone. We do not know why, so we tested every file alone in an empty folder.

7-Zip needs a plugin on Ubuntu

Our first 7-Zip test on Ubuntu passed 61 of 281 files. The 7-Zip package leaves out the code that unpacks compressed RAR data. 7-Zip listed our example and then printed Unsupported Method for the four packed files. It passed only the stored blob.bin.

The package 7zip-rar adds that code. With it, 7-Zip extracted all five files and passed 105 files. We did not test the Windows version of 7-Zip. If 7-Zip refuses a RAR file on Linux, check the plugin first.

With the plugin, 7-Zip crashed with a segmentation fault on 13 files. One is a 221 byte test file from rarfile with a solid RAR 3 layout. unrar and unar read that file without a problem. We report the crash and make no claim about other builds of 7-Zip.

Our script on the 281 files

Our script printed OK for 242 files and FLAG for 39. For RAR5 it printed OK for 98 and FLAG for 31. All four readers passed 41 of the 98 OK files, and no reader passed 12 of them. The script cannot check packed data, so OK is a verdict on structure only.

It flagged 31 RAR5 files, and at least one reader passed 12 of them. So a flag is a reason to look closer, and not a verdict. For the 144 older files it checks the signature and nothing else, and says so.

Readers differ on healthy files The four readers split on 102 of 281 files, and unar alone passed 22.
A short check is cheap Our 36 line script reads the signature, every header CRC32, the end block and the CRC32 of stored files.
Split sets need every part Alone, none of 66 volume parts passed in unrar or 7-Zip.
Not tested on Windows or macOS We opened nothing in File Explorer or on a Mac, so passes show sound structure for four readers only.

Read the study with care. It shows what four open readers do with 281 files from three test sets. Windows and macOS can be stricter or more lenient than any of them, and we had no copy of either. Files from other sources can differ from ours.

What Happens When a RAR File Is Damaged? 21 broken copies, and the four readers agreed on 10

We damaged one RAR file in 21 ways. The four readers agreed on 10 copies and split on 11. Our script flagged or warned on 13. Our own script restored 8 of the 18 copies that needed a repair, and a recovery record repaired 3 of 4 data tests.

The 21 copies come in three groups of 7. Group A changes the signature or a header. Group B changes the length of the file or how it was moved. Group C changes the content. Every copy changes one thing in example.rar, which is 3,160 bytes long and stores 5 files.

We asked three questions about every copy. What did every reader return, compared with its answer on the original, data and names together? Did our script flag it? Did one script bring back the original for all four readers?

Grid of 21 damaged copies of one RAR file against unrar, 7-Zip, bsdtar, unar, our check script and a repair test. The four readers agreed on 10 copies, our script flagged or warned on 13, and our 36 line script restored 8 of the 18 copies that needed it.
Figure 4. 21 damaged copies, four readers, our script and a repair test.

Copies that split the readers

A3 breaks the CRC32 of the main header and A4 breaks the one of the first file header. unar read both in full. unrar read both with a warning, and 7-Zip and bsdtar refused both. So a CRC32 is a rule that unar does not enforce on these headers.

A7 breaks the CRC32 of the end block, and B1 cuts the last byte, which is part of the end block. bsdtar and unar read A7 in full, and unrar and 7-Zip read it with a warning. For B1, unrar, 7-Zip and unar warned, and bsdtar read it in full.

A2 sets the version byte of the signature to 00, so the file looks like an older RAR file. unrar, 7-Zip and bsdtar refused it. unar exited with 0 and wrote no file. That silent answer is the worst kind, because nothing shows you that nothing was extracted.

B3 keeps only the main header, 24 bytes. bsdtar and unar exited with 0 and wrote no file, while unrar and 7-Zip refused. B2 cuts the file to half. bsdtar exited with 0 and wrote 1 of 5 files, and the other three readers refused it.

Copies that returned a changed file

C6 changes one stored byte in blob.bin, and C7 swaps two. unrar, 7-Zip and unar refused both. bsdtar exited with 0 and wrote all five files, and blob.bin had changed bytes. Of all our results this is the one to remember, because a wrong file came with no error.

B5 changes every line end into two bytes, the damage a text mode transfer can do. bsdtar exited with 0 and wrote one file that was wrong. The other three readers refused the copy. C4 changes a letter in a file name. All four readers extracted 5 files, and one was named bxob.bin.

The copies every reader refused

A1 breaks the first byte of the signature, B6 loses it, and A5 puts four junk bytes in front. All four readers refused all three. C1 flips bits in a packed file, C3 zeroes the second half and C5 changes a size, and all four refused those as well. That is 6 copies.

The junk test hides a detail. We added more bytes in front of a healthy file. unrar read it after 100 bytes of zeros, text or a marker, but not after 4. bsdtar read it after 1,000 zero bytes. 7-Zip and unar read none of our versions. RARLAB says readers search for the signature, and only some do.

The 8 copies our script passed

A6 sets the volume flag and fixes the CRC32, and B4 and B7 add bytes after the end. All four readers returned the original for all three, so the script is right to print OK. They are the only copies where every reader printed the same answer as on the original.

A2, C1, C2, C4 and C5 are the five that matter. They print OK and still fail somewhere. A2 fools the script because it reads the older signature as valid. C1 and C5 change packed or header bytes that the script cannot check. C2 and C4 change a field and a name, and the script cannot know what you expect.

A pass means the structure is sound and not that the data is right. Only a second reader, a hash from the sender or the files themselves show a changed byte.

Repairs that worked

Our script of 30 lines restored 8 of the 18 copies that needed a repair, byte for byte, for all four readers. It cuts anything in front of the signature, writes the first byte back and sets the version bytes. It also rewrites every header CRC32 and adds an 8 byte end block when one is missing.

It fixed A1, A2, A3, A4, A5, A7, B1 and B6. We checked every result with the four readers and a hash. The script rewrites CRC32 values, so use it on a copy. If a header CRC32 is wrong because the data is wrong, a new CRC32 hides the problem.

The official command rar r rebuilt 19 of the 21 copies. For 6 of the 18 that needed a repair, unrar and unar then read all five files, while 7-Zip warned and bsdtar still returned a different answer. No copy passed in all four readers after rar r alone.

What no command repaired

B2 and B3 lose content, C1, C3, C6 and C7 change or lose data, and B5 changes every line end. C2, C4 and C5 change a field that only you can check. No rule shows what the original bytes were, so ask for the file again.

A recovery record is the exception. We added one with rar a -rr3p, which made our file 921 bytes larger, from 3,160 to 4,081. rar r then repaired a changed byte, two swapped bytes and 512 zero bytes, and all four readers read the result. It could not repair 1,000 zero bytes or a file cut to half.

Readers disagree unrar, 7-Zip, bsdtar and unar gave different answers on 11 of 21 copies.
Headers can be rebuilt 8 copies with a broken signature or header came back byte for byte.
Exit 0 is not right bsdtar wrote a changed blob.bin for C6 and C7 and printed no error.
A recovery record helps About 920 bytes repaired a changed byte and 512 zero bytes.

Read the grid with care. Every copy changes one thing in one small archive. Damage in the wild changes many things at once. We opened no copy on Windows or macOS, and our repairs rely on rules that fit the files we made.

What Does Our Expert Say About RAR Files? A note from Neeraj Singh on trying a second reader

Test a RAR file with two readers before you trust it. Our four readers disagreed on 11 of 21 damaged copies, and bsdtar wrote a changed file for two of them with an exit code of 0.

Neeraj Singh

Expert insight

“A RAR file checks every header and every file with a CRC32, and our four readers still agreed on only 10 of 21 damaged copies. One reader wrote a changed file and printed no error. Test a RAR file with a second reader, keep the original untouched and add a recovery record to archives that matter.”

Neeraj Singh Manager, Tech Support & Operations 19+ years fixing Windows and system errors

Why one reader is not enough

A reader can return the wrong data without an error. bsdtar did that for C6 and C7, and unar exited with 0 and wrote nothing for A2 and B3. A refusal at least warns you that something is wrong. A silent result does not.

If your RAR file opens in the program you trust and the files look right, treat that as the best test. Use the readers on this page when it does not. unrar and 7-Zip refused the most copies, so they make the stricter second reader.

Copy your RAR file before you repair it. Work on the copy and keep the original untouched. Write down its SHA-256 hash first, so you can show later that the copy came back as it was.

How Do You Open a RAR File? Windows 11, a Mac and Linux, with the steps the makers list

Windows 11 24H2 opens a RAR file without extra software, per Microsoft. For Mac and Linux, use a reader from its maker. We tested four readers on Linux, and unar passed the most files, 149 of 281.

The table lists the programs that open a RAR file. Rows with version numbers are tools we tested on Linux. The Windows and macOS rows rest on the pages named in them, and we tested neither.

Programs that open RAR files
Program What it does
Windows File Explorer Microsoft says Windows 11 24H2 supports ZIP, RAR, 7z and TAR archives and does not support encrypted archives. We did not test it.
macOS Finder We found no Apple page that lists RAR, and we did not test a Mac. Use a reader from its maker, for example unar.
WinRAR The program from RARLAB. Microsoft names it for encrypted archives. We did not test it.
unrar 7.00 The free reader from RARLAB. It passed 116 of our 281 files.
7-Zip 23.01 Needs the 7zip-rar plugin on Ubuntu. With it, 7-Zip passed 105 files and read 3 of 21 damaged copies in full.
bsdtar 3.7.2 The libarchive reader. Passed 119 files, and wrote a changed file for two damaged copies without an error.
unar 1.10.1 The reader behind The Unarchiver. Passed 149 files, the most of the four.
The file command Version 5.45. It named 273 of our 281 files RAR archive data.

Open a RAR file on Windows 11

Microsoft lists the steps for zipped folders on Windows 11, version 24H2. The page says that Windows 11 24H2 supports ZIP, RAR, 7z and TAR archives. It also says that encrypted archives are not supported, and it names 7-Zip and WinRAR for those.

  1. Right click, or long press, the RAR file.
  2. Select Extract All, then follow the instructions on the screen.
  3. If Windows refuses the file, install 7-Zip or WinRAR from its maker and try again.
  4. For a split set, keep every part in one folder and open the first part.

Open a RAR file on a Mac

We did not test a Mac. We found no Apple page that lists RAR as a format Finder opens, so use a reader. unar is the command line reader behind The Unarchiver, and the Homebrew package is named unar. unrar from RARLAB also works on a Mac.

Open a RAR file on Linux

On Linux, our four readers worked from the command line. unrar x example.rar out/ unpacks the five files, and 7z x, bsdtar -xf and unar do the same. The extract steps show all four with output.

What to use for every task

Open a normal RAR file. Use the tool that comes with Windows 11 24H2, or WinRAR. Open one with a password. Microsoft names 7-Zip and WinRAR for Windows 11 24H2, and we tested neither with a password.

Open a RAR file that one reader refuses. Try a second reader. In our tests unar passed 22 files that no other reader passed, and bsdtar passed 12, so the same file can open in one and fail in another. Open a split set. Keep every part in one folder.

Install programs from their makers. Take WinRAR and unrar from RARLAB and 7-Zip from its own page. A free web unpacker receives your files, so try the steps on this page first.

How Do You Check a RAR File? Six steps and a script of 36 lines

Check a RAR file in six steps. Read the first bytes, list the files, use a script and compare two readers. Our 36 line script printed OK for 242 of 281 files and flagged or warned on 13 of 21 damaged copies.

First reads of a RAR file need no Python. The unrar t command tests every file against its CRC32, and unrar l lists the names. We used two readers on example.rar, and both passed. A damaged copy gets different answers.

List the five files in one healthy RAR file
unrar l example.rar
Archive: example.rar
Details: RAR 5

 Attributes      Size     Date    Time   Name
----------- ---------  ---------- -----  ----
 -rw-r--r--      1500  2026-10-31 06:07  blob.bin
 -rw-r--r--      2664  2026-10-31 06:07  config.json
 -rw-r--r--      1898  2026-10-31 06:07  notes.md
 -rw-r--r--      3393  2026-10-31 06:07  readme.txt
 -rw-r--r--      2053  2026-10-31 06:07  sales.csv
----------- ---------  ---------- -----  ----
                11508                    5
Two ways to test one healthy RAR file
unrar t example.rar
Testing archive example.rar
Testing  blob.bin  OK
Testing  config.json  OK
Testing  notes.md  OK
Testing  readme.txt  OK
Testing  sales.csv  OK
All OK
7z t example.rar | tail -4
Everything is Ok
Files: 5
Size:       11508
Compressed: 3160

Both commands pass our example. They work in different ways, so read the lines above the last one too. A damaged copy shows the difference.

One damaged copy, tested by two readers
unrar t C6.rar
Testing archive C6.rar
Testing  blob.bin
blob.bin  - checksum error
Testing  config.json  OK
Testing  notes.md  OK
Testing  readme.txt  OK
Testing  sales.csv  OK
Total errors: 1
7z t C6.rar | tail -3
ERROR: CRC Failed : blob.bin
Sub items Errors: 1
Archives with Errors: 1

C6 changes one stored byte in blob.bin. Both readers name that file and report one error. bsdtar, used on the same copy, wrote all five files and printed no error, so a test that names the file is worth more than an extract.

Check RAR files with Python

The script reads the signature and follows every block. For every header it compares the CRC32, and for stored files it compares the data CRC32. It reads an older RAR file by its signature only.

It warns about bytes before the signature and bytes after the end. It prints OK, WARN or FLAG. It never changes a file.

Check the signature, every header and the stored files of a RAR file
import sys, zlib
S5, S4 = b'Rar!\x1a\x07\x01\x00', b'Rar!\x1a\x07\x00'
def vint(b, i):
    v = s = 0
    while True:
        c = b[i]; i += 1; v |= (c & 0x7f) << s; s += 7
        if not c & 0x80: return v, i
def peek(p):
    b = open(p, 'rb').read(); k = b.find(S5, 0, 1 << 20)
    if k < 0:
        return 'OK rar4 signature only' if b.startswith(S4) else 'FLAG no RAR5 signature'
    msg = ['WARN %d bytes before signature' % k] if k else []
    i = k + 8; n = 0; last = 0
    while i + 7 <= len(b):
        try:
            hs, j = vint(b, i + 4); t, _ = vint(b, j)
        except IndexError: return 'FLAG cut inside a header at %d' % i
        if zlib.crc32(b[i + 4:j + hs]) & 0xffffffff != int.from_bytes(b[i:i + 4], 'little'):
            return 'FLAG header CRC wrong at %d' % i
        fl, q = vint(b, j + 1); ds = 0
        if fl & 1: _, q = vint(b, q)
        if fl & 2: ds, q = vint(b, q)
        if t == 2 and ds:
            ff, q = vint(b, q); _, q = vint(b, q); _, q = vint(b, q)
            if ff & 2: q += 4
            if ff & 4:
                crc = int.from_bytes(b[q:q + 4], 'little'); ci, _ = vint(b, q + 4)
                if (ci >> 7) & 7 == 0 and zlib.crc32(b[j + hs:j + hs + ds]) & 0xffffffff != crc:
                    return 'FLAG stored data CRC wrong at %d' % (j + hs)
        i = j + hs + ds; n += t == 2; last = t
        if i > len(b): return 'FLAG data goes past the end'
        if t == 5: break
    if last != 5: return 'FLAG no end block'
    return ('WARN ' + msg[0][5:] if msg else 'OK') + ' %d files' % n if not msg else msg[0] + ', %d files' % n
if __name__ == '__main__':
    for p in sys.argv[1:]: print(p.split('/')[-1], peek(p))

Here is what it printed for our example and for three damaged copies.

One healthy RAR file and three damaged copies
python3 rar_peek.py example.rar
example.rar OK 5 files
python3 rar_peek.py A3.rar C6.rar A5.rar
A3.rar FLAG header CRC wrong at 8
C6.rar FLAG stored data CRC wrong at 59
A5.rar WARN 4 bytes before signature, 5 files

A healthy answer gives the number of files. A3 has a wrong header CRC32, and C6 has a stored file whose CRC32 fails. A5 has four junk bytes in front and gets a warning, because all five files can still be found.

What the script found in our files

Our script on healthy and damaged RAR files
Result Cases
Passed (242 of 281 files) The start is right, every header CRC32 matches and the end block is there. 144 of these are the older kind, where the script checks only the signature.
Flagged (39 of 281 files) Messages include a header CRC32 that does not match, a stored file whose CRC32 does not match and no end block. At least one reader passed 12 of the 31 flagged RAR5 files.
Signature (A1, B6) The script prints no RAR5 signature, because the first byte is wrong or gone.
Main and file headers (A3, A4) The script prints a header CRC32 that is wrong, and it names the byte position.
End block (A7, B1, B3) A7 and B1 print a wrong header CRC32 at byte 3152, where the end block starts. B3 prints no end block.
Cuts and zeroes (B2, C3) Both print a wrong header CRC32 at byte 1559, where the file header after the cut or the zeroes starts.
Stored data (B5, C6, C7) The script prints a stored file whose CRC32 does not match, at byte 59.
Warned (A5) Four bytes before the signature, and all five files are still found.
Passed but changed (A2, C1, C2, C4, C5) These print OK. The script cannot check packed data, and it cannot know what you expect in a name or a field.

The script has limits. It cannot test packed data, and it cannot see that C4 changed a name. It flagged 12 RAR5 files that at least one reader passed, so flags are reasons to look closer and not verdicts. The repair routes fix the kinds of damage we tested.

Check order for any RAR file

  1. Copy your RAR file, write its SHA-256 hash and work on the copy.
  2. Read the first bytes with xxd -l 8. 5261 7221 1a07 0100 is RAR5, and 1a07 00 is the older start. See the start table.
  3. List the files with unrar l and compare with the list from a second reader.
  4. Use our script. The first word is OK, WARN or FLAG, and a flag names the problem.
  5. Test the files with unrar t or 7z t and compare the answers.
  6. Compare file names and sizes with what you expect. We opened nothing on Windows or macOS, so passes show sound structure for four readers only.

Is a RAR File Safe to Open? Reading the list is safe, and extracting needs care

Reading the list of a RAR file starts nothing, so it is safe. The risks come after. Extraction can overwrite files, and a program inside the RAR file starts only when you start it. IANA says security issues for the type have not been assessed.

We started nothing. Our readers listed, tested and extracted files into empty folders, and the test files are public. We scanned none for malware, and we opened none on Windows or macOS.

The IANA record for application/vnd.rar says security issues have not been assessed. That is a gap in the record and not a finding about RAR files, so treat a RAR file from a stranger like any other archive.

Reading the list Safe. unrar l and our script read the headers and unpack nothing.
Writing down hashes Safe. A hash shows which copy you have.
Extracting into a folder Use an empty folder, because extracting can overwrite files that have the same names.
Passwords Microsoft says Windows 11 24H2 does not support encrypted archives. Use 7-Zip or WinRAR, and keep the password apart from the file.
Uploading to a free unpack site The site gets your files. Use a program you installed from its maker.
Starting a program from inside Opening a RAR file starts nothing, but a program inside it starts when you double click it.

Read the size before you extract

The listing shows the unpacked size before anything is written. Our example stores 11,508 bytes of files in 3,160 bytes, and unrar l prints every size.

A RAR file whose listing shows a size you did not expect is worth a second look before you extract anything. We did not test archives made to unpack to huge sizes, so we give no limit.

A RAR file from someone else

Open the list first, and read the names. Look at the endings of the files inside. A name like invoice.pdf.exe is a program. Extract into an empty folder, and scan the folder before you open anything.

Share a RAR file with a helper

Send the RAR file and the output of our script, and not the files inside it. The first word of the output shows a helper whether the structure is sound. Keep the original, and send a copy.

Not sure? Check it first. Copy the hash, read the first bytes with our check steps and ask the sender for a fresh file if anything looks wrong. Extract last, into an empty folder.

Why Will Your RAR File Not Open? Eight causes, and what to do about every one

Most RAR files that will not open fail for one of eight reasons. Read the first bytes, use the script and try a second reader. Our script flagged or warned on 13 of 21 damaged copies, and our own script restored 8 of the 18 that needed a repair.

We damaged one RAR file in 21 ways and tested two repair routes on the copies that needed one. The table groups what we saw into eight causes.

Every row says what happens to your RAR file and what to try next. Fixes work on copies, and none changes the original. We opened no repaired file on Windows or macOS, so a repaired file shows only that four Linux readers can read it.

Eight causes of RAR files that will not open
Cause Result and fix
A broken first signature or a lost first byte (1) A1 breaks the first byte of Rar! and B6 loses it. All four readers refused both. Fix: Write the first byte back with our script. Both came back byte for byte.
Bytes in front of the archive (2) A5 puts four junk bytes in front. All four readers refused it, although every block after them was fine. Fix: Cut the bytes in front with our script. It came back byte for byte.
A wrong version byte (3) A2 sets the last signature byte to 00, so the file looks like an older RAR file. unrar, 7-Zip and bsdtar refused it, and unar exited with 0 and wrote no file. Fix: Set the version byte back with our script.
A wrong header CRC32 (4) A3 breaks the CRC32 of the main header and A4 the one of the first file header. unar read both in full, unrar warned, and 7-Zip and bsdtar refused both. Fix: Rewrite the CRC32 values with our script, on a copy.
A broken or lost end block (5) A7 breaks the end block CRC32 and B1 cuts its last byte. unrar and 7-Zip warned for both, and bsdtar read both in full. B3 keeps only the main header. Fix: Our script fixes A7 and B1. For B3, ask for the file again.
Extra bytes after the end (6) B4 and B7 add bytes after the end, and A6 sets the volume flag. All four readers returned the original for all three. Fix: None needed for these readers.
Cut or changed data (7) B2 cuts the file, C1, C3 and C5 change packed bytes or a size, C6 changes a stored byte, C7 swaps two and B5 changes every line end. Fix: None. Ask for the file again, or repair from a recovery record.
A changed name or field (8) C4 changes a letter in a name, and all four readers extracted a file with the wrong name. C2 changes a field, and 7-Zip and unar warned. Fix: None. Compare the names with what you expect.

When the file is not damaged

Four things look like a damaged RAR file and are not. A password makes every reader refuse. A split set is only one piece. A reader without its plugin cannot unpack compressed data. A file that ends in .rar can be another format.

A password Of our 20 password protected files, unrar passed 1, unar 1, bsdtar 2 and 7-Zip none. We gave no password. Microsoft says Windows 11 24H2 does not support encrypted archives.
A split set Alone, none of our 66 volume parts passed in unrar or 7-Zip. Keep every part in one folder and start with the first.
A missing plugin On Ubuntu, 7-Zip printed Unsupported Method for packed files until we installed 7zip-rar. Check the plugin first.
Another format Eight of our 281 files do not start like a RAR file. Read the first bytes and use the program that fits.

Repairs we tested

A script of 30 lines covers the fixes that need our own code. It takes the damaged RAR file and a name for the new file. The official route is rar r, which rebuilds a file from its own data and from a recovery record when there is one.

rar_fix.py, 30 lines
import sys,zlib,struct
SIG=b'Rar!\x1a\x07\x01\x00'
def vint(b,i):
    v=s=0
    while True:
        c=b[i];i+=1;v|=(c&0x7f)<<s;s+=7
        if not c&0x80:return v,i
def fix(b):
    if b[:6]==SIG[:6] and b[:8]!=SIG: b=SIG+b[8:]   # 0 version bytes broken
    k=b.find(SIG,0,1<<20)                      # 1 find the signature, drop bytes in front
    if k>0: b=b[k:]
    elif k<0:
        if b[1:8]==SIG[1:]: b=SIG[:1]+b[1:]    # first byte broken
        elif b[:7]==SIG[1:]: b=SIG[:1]+b       # first byte lost
        else: raise SystemExit('no signature')
    out=bytearray(b[:8]); i=8
    while i+7<len(b):                          # 2 rewrite every header CRC
        try:
            hs,j=vint(b,i+4); end=j+hs; t,k2=vint(b,j); fl,k2=vint(b,k2)
            ds=0
            if fl&1: _,k2=vint(b,k2)
            if fl&2: ds,k2=vint(b,k2)
        except IndexError: break
        if end>len(b) or t>5: break
        out+=struct.pack('<I',zlib.crc32(b[i+4:end])&0xffffffff)+b[i+4:end+ds]; i=end+ds
        if t==5: return bytes(out)
    end=bytes([3,5,4,0])                       # 3 add the 8 byte end block when it is missing
    return bytes(out)+struct.pack('<I',zlib.crc32(end)&0xffffffff)+end
if __name__=='__main__':
    open(sys.argv[2],'wb').write(fix(open(sys.argv[1],'rb').read()))
Commands for four kinds of damage
# 1  first signature (A1), first byte (B6), bytes in front (A5), end block (B1)
python3 rar_fix.py A1.rar A1_fixed.rar
python3 rar_fix.py A5.rar A5_fixed.rar
python3 rar_fix.py B1.rar B1_fixed.rar
python3 rar_fix.py B6.rar B6_fixed.rar
# compare with the original
sha256sum example.rar A1_fixed.rar A5_fixed.rar B1_fixed.rar B6_fixed.rar | cut -c1-12
58ce98e8bc9f
58ce98e8bc9f
58ce98e8bc9f
58ce98e8bc9f
58ce98e8bc9f

The last lines compare hashes. The first 12 characters match for the original and the four repaired files, so every repaired file equals the original byte for byte.

Fix RAR files that will not open, step by step

We tested the steps on Linux with unrar 7.00. We opened no file on Windows or macOS, and the steps keep the original untouched at every point.

  1. Copy your RAR file, write its SHA-256 hash and work on the copy.
  2. Name the start with xxd -l 8 and the four kinds of start. A RAR5 file starts with 5261 7221 1a07 0100.
  3. Use the check script on this page. A flag or warning names the problem.
  4. Try a second reader. unar passed the most of our files, and unrar was the strictest, so use both.
  5. Match the answer to a cause in the table above and try its fix on the copy.
  6. If one fix fails, do not stack another on top. Go back to the copy and try the next cause.
  7. Test the result with two readers and compare the file names and sizes with what you expect.

What to send a helper

Short messages get faster answers. Include the details below and add the script output. Its first word gives OK, WARN or FLAG.

A message that gets an answer
Subject: My RAR file will not open
File: name, size in bytes and SHA-256 hash
Start: the output of xxd -l 32
Check: the output of rar_peek.py
Program: name, version and the exact words of the error
Source: where the file came from, and how it was sent

What no step can fix

Cut files No command restored B2 or B3. Ask for the file again or look for an older copy.
Changed data C1, C3, C6 and C7 change or lose bytes, and no rule shows the original bytes. B5 changes every line end.
A recovery record It repaired a changed byte, two swapped bytes and 512 zero bytes, and it cost 921 bytes on our file. It must be added before the damage.
Readers that disagree If two readers disagree, trust neither. Try a third, then ask for a new file.
Names that do not match C4 shows that one name can change a letter. Compare listings with what you expect before you extract.
Wrong endings A file named .rar can use any layout. Name the kind first.

Do not try online repair sites. Sites that offer to fix any RAR file receive your upload. The file can contain private documents. Try the steps above on a copy first.

How Do You Extract Files From a RAR File? Four commands that gave the same five files

Four open readers extracted example.rar into the same five files, byte for byte. Use unrar x, 7z x, bsdtar -xf or unar, and always use an empty folder.

People extract a RAR file to get the files out. Windows does this with the steps in the open part. The commands below do the same from a terminal, and we tested all four on Linux.

Extract with unrar

unrar x keeps the folder structure and writes into the folder you name. Add -idp to hide the percent counter.

Extract the five files into a new folder
unrar x -idp example.rar x_demo/
UNRAR 7.00 freeware      Copyright (c) 1993-2024 Alexander Roshal
Extracting from example.rar
Creating    x_unrar2                                                  OK
Extracting  x_unrar2/blob.bin                                         OK 
Extracting  x_unrar2/config.json                                      OK 
Extracting  x_unrar2/notes.md                                         OK 
Extracting  x_unrar2/readme.txt                                       OK 
Extracting  x_unrar2/sales.csv                                        OK 
All OK

To read one file without writing anything, send it to the screen. The command below prints the first three lines of sales.csv. Nothing lands on the disk.

Read one file from a RAR file
unrar p -inul example.rar sales.csv | head -3
id,item,qty,price
0,item0,6,25.71
1,item1,7,8.91

Compare four readers

We extracted example.rar with all four readers into four empty folders. We then hashed every file in every folder and hashed the list of hashes. All four folders gave the same value.

Four readers, one result
unrar x -idp -y example.rar x_unrar/
7z x -y -bd -bso0 -ox_7z example.rar
bsdtar -xf example.rar -C x_bsd
unar -q -D -o x_unar example.rar
for d in x_unrar x_7z x_bsd x_unar; do (cd $d && find . -type f | sort | xargs sha256sum | sha256sum | cut -c1-12); done
88449c520381
88449c520381
88449c520381
88449c520381

The four lines are the same, so the five files match byte for byte. That is true for a healthy RAR file. The damaged copies show that the readers can differ when a file is hurt.

Passwords and split sets

We gave no password in any test, so we cannot say how the four readers treat a wrong one. Microsoft says Windows 11 24H2 does not support encrypted archives, and names 7-Zip and WinRAR for them. We tested neither with a password.

Split sets need every part. In our first test with all files in one folder, unrar passed 63 of 66 parts, and alone it passed none. Put every part in one folder and open the first.

Empty folder first Extraction can overwrite files with the same names. Make a new folder for every RAR file.
List before you extract unrar l shows names and sizes and writes nothing.
Test the data unrar t checks every file against its CRC32.
Use a second reader On a healthy RAR file all four gave the same files. On a damaged RAR file they split on 11 of 21 copies.

Keep the RAR file. Extraction does not change it, but you can need it again if a file inside proves to be damaged.

How Does a RAR File Differ From ZIP, 7Z and TAR Files? Close neighbors, and the first bytes separate them

RAR, ZIP, 7Z and TAR are separate archive formats, and Microsoft says Windows 11 24H2 supports all four. The ending names the format, and the first bytes confirm it. A RAR file starts with Rar!, and a ZIP file starts with PK.

The table lists the neighbors of a RAR file. Every row ends with its source. Rows for ZIP, 7Z and TAR rest on Microsoft and Wikipedia, because we read no files of those kinds in this study.

RAR, ZIP, 7Z and TAR compared
Type What separates it
RAR A closed archive format by Eugene Roshal, first released in March 1993. Microsoft says Windows 11 24H2 supports it. Source: Wikipedia and Microsoft.
ZIP An archive format from 1989 with a directory at the end. Microsoft says Windows 11 24H2 supports it. Source: Wikipedia and Microsoft.
7Z The native format of 7-Zip. Microsoft says Windows 11 24H2 supports it. 7-Zip also reads RAR files with a plugin on Ubuntu. Source: Microsoft and our tests.
TAR An archive format that Windows 11 24H2 supports. We read no TAR files, but bsdtar extracted our RAR files. Source: Microsoft and our tests.

RAR or ZIP

Both are archives, and Windows 11 24H2 supports both, per Microsoft. They are different formats, so a RAR file does not start with PK. Read the ZIP file page for that format.

RAR or 7Z and TAR

The same Microsoft page lists 7z and TAR. 7-Zip, with its plugin, read 105 of our 281 RAR files. Wikipedia notes the RAR compression is proprietary, which is why free tools read RAR files and few write them.

RAR or EXE and DMG

A RAR archive can follow a program. RARLAB says readers search for the signature up to the biggest self extracting module, so a file that ends in .exe can contain a RAR archive. A DMG file is the disk image a Mac mounts, and it is a different format.

Which one do you have

ZIP archives Read the ZIP file page for the archive format that opens everywhere.
Programs Read the EXE file page for the Windows program format.
Mac disk images Read the DMG file page for the disk image a Mac downloads.
Other types Browse the resource library for more formats.

What Is the RAR File Format Made Of? The facts we could check, and where they came from

A RAR file stores a signature, a main header, file headers with data and an end block. Facts below come from our own checks of 281 files and 21 damaged copies. Sources are Wikipedia, IANA, RARLAB, Microsoft and the three test projects.

Facts about RAR files
Part What we could check
Maker Eugene Roshal, per Wikipedia. The first release was in March 1993, and the name stands for Roshal Archive.
Name IANA registers the media type application/vnd.rar with the extension .rar. The file command printed application/x-rar for our example.
First bytes IANA lists 52 61 72 21 1A 07 00. 129 of our 281 files start with the RAR5 form, 52 61 72 21 1A 07 01 00, and 144 with the older one.
Layout A signature, a main header, then a header and data for every file and an end block. Every block starts with a CRC32 and a size.
Block types RARLAB lists 1 main, 2 file, 3 service, 4 encryption and 5 end of archive.
Methods The method is stored in the compression info of the file header. 0 means stored. Our example packs 11,508 bytes into 3,160 bytes, and its stored file blob.bin stays at 1,500 bytes.
Sizes Our files are 7 to 1,081,705 bytes long, with a median of 508.
Security Wikipedia says RAR5 uses AES 256. IANA says security issues for the type have not been assessed.
Checksum CRC32 on every header and every file. All four readers refused or warned on most copies with changed bytes, and bsdtar wrote a changed blob.bin for C6 and C7.
Recovery A recovery record is a service header named RR, per RARLAB. It added 921 bytes to our file, and rar r repaired three kinds of damage with it.
Our tests 281 files, 21 damaged copies, 4 readers, 2 repair routes and a script of 36 lines. unrar 7.00, 7-Zip 23.01, bsdtar 3.7.2, unar 1.10.1, rar 7.00, Python 3.13 and file 5.45 on Linux.

About the values we list

Facts about the layout come from our own reading of one example file and 281 test files, and from the pages we name. RARLAB publishes notes on the RAR5 layout, and we claim no field that our files do not show.

Where we found no record, we say so. We tested no password that opens a file and no version of Windows or macOS.

What we left out

We opened no file in File Explorer or on a Mac. We used no web unpacker and scanned no file for malware. Our readers and scripts worked on Linux, and Windows and macOS can accept or refuse files that they treat differently.

All 281 files come from the libarchive, junrar and rarfile test sets, and many are built to break readers. Our damaged copies come from one small archive and change one thing at a time. Files from other sources can differ from ours.

Sources checked

For the format, see the Wikipedia article on RAR, the IANA record for application/vnd.rar and the RARLAB technote. For opening files, see the Microsoft page on zip and unzip.

For the test files, see the libarchive project, the junrar project and the rarfile project. Every count on this page came from files and scripts in our research folder.

Frequently Asked Questions About RAR Files

What is a RAR file?

A RAR file is an archive that packs files and folders into one file and shrinks them. Wikipedia says Eugene Roshal made the format and released it in March 1993. IANA registers the type application/vnd.rar. Every header and every file has a CRC32.

How do I open a RAR file?

On Windows 11 24H2, right click the file and select Extract All, per Microsoft. Older Windows needs WinRAR or 7-Zip. On a Mac or Linux, use unar, unrar or 7-Zip. We tested four Linux readers and none of the Windows or Mac steps.

How do I open a RAR file on Windows?

Microsoft says Windows 11 24H2 supports ZIP, RAR, 7z and TAR archives. It does not support encrypted archives, and Microsoft names 7-Zip and WinRAR for those. Install either from its maker if Windows refuses your file.

How do I open a RAR file on a Mac?

We tested no Mac and found no Apple page that lists RAR. Use a reader. unar and unrar both passed our example, and the Homebrew package for unar is named unar. Install programs from their makers.

Is a RAR file safe to open?

Reading the list starts nothing, so it is safe. Extracting can overwrite files with the same names, so use an empty folder. A program inside a RAR file starts only when you start it. IANA says security issues for the type have not been assessed.

What is the difference between RAR and ZIP?

They are separate archive formats, and Microsoft says Windows 11 24H2 supports both. A RAR file starts with Rar! and a ZIP file with PK. Wikipedia says the RAR compression is proprietary. Read the ZIP file page for that format.

Why will my RAR file not open?

Eight causes cover what we saw in damaged files. They are a broken start, bytes in front, a wrong version byte, a wrong header CRC32, a broken end, extra bytes, changed data and a changed name or field. A password, a split set or a missing plugin can also stop a reader.

How can I check if a RAR file is damaged?

Read the first bytes, test the files with unrar t and compare two readers. Our script also checks every header CRC32 and the CRC32 of stored files. It flagged or warned on 13 of 21 damaged copies, so only a second reader finds the rest.

Can a damaged RAR file be repaired?

Some damage can be repaired. Our script restored 8 of the 18 copies that needed a repair, byte for byte. Cut files and changed data did not come back. A recovery record repaired a changed byte and 512 zero bytes. Keep the original.

Do all readers agree on a damaged RAR file?

No. unrar, 7-Zip, bsdtar and unar agreed on only 10 of our 21 damaged copies. bsdtar wrote a changed file for two copies and printed no error, and unar exited with 0 and wrote nothing for one. Try a second reader before you trust a result.

What is a recovery record in a RAR file?

It is extra data that lets WinRAR or rar repair the file later. RARLAB stores it as a service header named RR. It added 921 bytes to our 3,160 byte file. rar r then repaired a changed byte, two swapped bytes and 512 zero bytes.

What MIME type is a RAR file?

IANA registered application/vnd.rar on 2016-07-14, and the file command printed application/x-rar for our example. IANA lists the older signature, 52 61 72 21 1A 07 00. Our newer files start with 52 61 72 21 1A 07 01 00.

Still Stuck With a RAR File? Six routes out, depending on what went wrong

Your RAR file will not open

Read the first bytes and use the check script. The cause table lists what to try in order.

You do not know the kind

The first bytes table names the kind, and the neighbors name the formats that look alike.

Is it a ZIP file? The guide to ZIP files covers the archive format that opens everywhere.

Is it a program? The guide to EXE files covers the Windows program format.

Is it a Mac disk image? The guide to DMG files covers the image that a Mac mounts.

Is it a file type you do not know? Browse the file extension resource library, or send it on the submit a file type page.

Do you need the format facts? Read the format part for the layout, the signatures and the sources of RAR files.