| The archive cannot be opened | The file may be incomplete, corrupted, mislabeled or encoded with an unsupported variant. | Check its original source and signature, download it again and try recovery only after preserving the original. After retrying, compare the resulting file count and sizes with any manifest supplied by the sender. |
| The archive type is not recognized | A renamed file or unusual compression header does not match a supported signature. | Confirm the extension and actual format; use a specialist tool for obscure DMG, WIM or ARJ variants. Record the exact error and affected archive format so support can distinguish variant issues from corruption. |
| RAR or 7Z decoding fails | The WebAssembly engine may not have loaded, the file may be truncated or its features unsupported. | Use a current browser, allow the decoder to load and retry a known-good copy on a device with sufficient memory. Avoid deleting the original archive until the extracted result has been checked for completeness. |
| Password is rejected | The password may be incorrect or the archive may use unsupported encryption or damaged headers. | Check case and special characters; request the correct password and test the archive with a compatible dedicated extractor. After retrying, compare the resulting file count and sizes with any manifest supplied by the sender. |
| I do not have the archive password | The contents are encrypted and cannot be read without valid authorization credentials. | Ask the owner for the password or an authorized unencrypted copy; do not assume recovery mode bypasses encryption. Record the exact error and affected archive format so support can distinguish variant issues from corruption. |
| Extraction stops midway | An entry could be corrupt or browser memory may be exhausted. | Try a smaller selection, close unused tabs, review the damaged entry and switch to desktop software for large jobs. Avoid deleting the original archive until the extracted result has been checked for completeness. |
| The browser tab freezes | Large expanded data, solid archives or many entry previews can consume memory and CPU. | Limit selections, avoid full previews, free device resources and retry on a desktop browser. After retrying, compare the resulting file count and sizes with any manifest supplied by the sender. |
| An extracted file is empty | The original archive entry may have zero bytes, failed integrity checks or suffered truncation. | Check the listed uncompressed size, retry a fresh source and compare results with the sender. Record the exact error and affected archive format so support can distinguish variant issues from corruption. |
| Downloaded output is ZIP rather than separate files | Multiple selections are packaged into a fresh archive for convenient download. | Choose a single entry for a direct file download or extract the resulting ZIP with an archive utility. Avoid deleting the original archive until the extracted result has been checked for completeness. |
| Folders look flattened | The browser or downstream unzip tool may present or save paths differently. | Inspect paths inside the generated ZIP and use the destination extractor option that preserves directory structure. After retrying, compare the resulting file count and sizes with any manifest supplied by the sender. |
| Preview is blank | The entry might be a binary, encrypted, damaged or unsupported preview format. | Download it only if trusted and inspect it with a suitable viewer; do not execute unfamiliar files. Record the exact error and affected archive format so support can distinguish variant issues from corruption. |
| PDF or image preview looks different | Preview rendering may not support all fonts, color profiles or metadata. | Open the extracted file in a dedicated application and confirm the data before assuming it is damaged. Avoid deleting the original archive until the extracted result has been checked for completeness. |
| Security scan flags a legitimate script | Heuristics detect potentially active file types and can produce false positives. | Verify origin and purpose, inspect the code and use a full security scanner if needed. After retrying, compare the resulting file count and sizes with any manifest supplied by the sender. |
| No warning appears for a suspicious file | Heuristic scanning does not detect every malicious or unusual payload. | Treat unknown files as untrusted and scan them with appropriate endpoint protection. Record the exact error and affected archive format so support can distinguish variant issues from corruption. |
| A zip-bomb warning appears | The archive claims a very large expanded size compared with its compressed bytes. | Avoid full extraction until requirements are checked and ensure adequate safe resource limits. Avoid deleting the original archive until the extracted result has been checked for completeness. |
| Duplicate scan is incomplete | Hashing was limited by size or processing budget. | Review the scanned subset and use a full dedicated hash check if complete deduplication is important. After retrying, compare the resulting file count and sizes with any manifest supplied by the sender. |
| Two same-named files differ | Identical filenames do not guarantee matching contents, especially across folders. | Compare sizes and complete content hashes before deleting either copy. Record the exact error and affected archive format so support can distinguish variant issues from corruption. |
| Recovery mode misses files | Corruption, missing volumes or damaged compressed blocks may make entries unrecoverable. | Keep the source, obtain remaining parts or backups and record which entries failed. Avoid deleting the original archive until the extracted result has been checked for completeness. |
| CRC or checksum mismatch persists | Decompressed bytes do not match the checksum expected by the archive. | Try a clean copy; do not rely on the affected file without checking its contents. After retrying, compare the resulting file count and sizes with any manifest supplied by the sender. |
| Imported archive URL does not load | The remote site may block cross-origin requests, require credentials or be temporarily unavailable. | Download the archive locally from the trusted source and choose it from your device. Record the exact error and affected archive format so support can distinguish variant issues from corruption. |