This page covers common issues with ZIP Extractor. If you don't see what you need, check the FAQ or contact support.
Error reading archive file
ZIP Extractor was unable to read the contents of your archive. The file may be corrupted, truncated, or in a format variant that cannot be processed.
Common causes
Corrupted or damaged archive. The file's internal structure is broken. This can happen if the file was modified, partially overwritten, or stored on failing media.
Incomplete download. The file may not have finished downloading. If the download was interrupted by a network error, browser crash, or timeout, the resulting file will be truncated and unreadable.
Unsupported format variant. Some archive formats have multiple versions or extensions. For example, certain ZIP64 edge cases, self-extracting archives (.exe), split or spanned archives (.z01, .z02), or archives created with non-standard tools may use features that ZIP Extractor does not support.
Wrong file type. The file may not actually be an archive. If a file has a .zip, .rar, .7z, or .tar extension but contains different data (for example, a renamed image or document), it cannot be read as an archive.
Encrypted archive header. Some RAR and 7z archives encrypt the file listing in addition to the file contents. If the archive header is encrypted, ZIP Extractor cannot read the file listing without the password.
What you can do
Re-download the file. If you received the file from the internet, email, or a shared link, download it again. A fresh download often resolves issues caused by incomplete transfers.
Verify the file size. Compare it to the size the source reports. If it's significantly smaller, the download was likely incomplete.
Try opening the file with another tool. If a desktop application such as 7-Zip, WinRAR, or The Unarchiver can open the file, it may use a format variant that ZIP Extractor doesn't yet support. You can extract the files with that tool instead.
Ask the sender to re-create the archive. If someone sent you the file, ask them to create a new archive using standard ZIP compression (Deflate method) and send it again.
Technical details
The error details below the message include internal diagnostics (like a stack trace) that can help identify the specific failure. If you contact support, include these details or a screenshot.
The file you opened is zero bytes in size. A valid archive must contain at least a small amount of structural data, so a zero-byte file cannot be read as an archive.
What you can do
Download the file again from the original source. The most common cause of a zero-byte file is an incomplete or failed download. Try downloading the file again. If you received it as an email attachment, try re-downloading the attachment.
Check the file on your computer. Right-click the file and check its properties or "Get Info." If the file size shows 0 bytes, the file itself is empty.
Ask the sender to re-share the file. If someone shared this file with you, their upload may have failed, leaving just a placeholder behind. Ask them to re-upload or re-share the original file.
Check Google Drive for sync issues. If the file is on Google Drive, it may not have synced correctly from the sender's device. The file owner can verify the file size in Drive and re-upload if needed.
Why does this happen?
A zero-byte file is a file that has a name but no content. This usually happens when a download is interrupted before any data transfers, or when a file transfer or sync fails silently and leaves a placeholder behind. Downloading the file again from the original source almost always resolves the issue.
Your browser ran out of memory while reading the archive. ZIP Extractor runs in your browser, so it's limited by the memory the browser makes available to a single tab.
What you can do
Close other tabs and applications. Each open tab uses memory. Closing tabs you aren't using frees memory for ZIP Extractor.
Try a different browser. Some browsers allocate more memory per tab than others. Chrome and Edge typically handle larger files well.
Use a device with more RAM. If possible, try opening the file on a desktop or laptop with at least 8 GB of RAM.
Split the archive. If you created the archive yourself, try splitting it into smaller parts (for example, under 1-2 GB each).
Why does this happen?
Web browsers put memory limits on each tab to keep the overall system stable. Very large files (typically over 2-4 GB, depending on the device) can push past these limits.
A few things can prevent ZIP Extractor from downloading a file from Google Drive.
Check your internet connection
Make sure you're connected to the internet and that your connection is stable. Try loading another website to confirm.
Sign in with the correct Google account
If the file belongs to a different Google account than the one you're signed in with, ZIP Extractor may not have permission to access it. Click Retry and choose the correct account when prompted.
Check that the file still exists
If the file was deleted, moved to trash, or the sharing link was revoked, it can no longer be downloaded. Ask the file owner to confirm it's still available.
File may be too large for direct download
Very large files on Google Drive can time out during download. Try again; the second attempt often works. If the problem persists, download the file to your computer first, then open it in ZIP Extractor using the local file option.
Disable browser extensions
Ad blockers, privacy extensions, or VPNs can interfere with Google Drive downloads. Try disabling extensions temporarily, or open ZIP Extractor in an Incognito/Private window.
Google Drive has temporarily limited downloads of this file. Google enforces per-file download quotas to prevent excessive bandwidth usage. When too many people download the same file in a short time, further downloads are blocked temporarily.
What you can do
Wait and try again later. The download quota resets automatically over time. Waiting a few hours (or up to 24 hours) usually resolves the issue.
Download the file directly from Google Drive. Open the file in Google Drive, download it to your computer, and then open it in ZIP Extractor using the local file option.
Ask the file owner for help. The file owner can make a copy of the file in their Drive, which resets the download quota. They can also share the file through a different method.
Why does this happen?
Google Drive limits how frequently a single file can be downloaded across all users. Popular shared files are more likely to hit the quota, which is applied per file rather than per user account.
You may be on a cellular data connection. Opening a ZIP file downloads the entire file to your browser before extraction can begin. On a limited data plan, that could use a noticeable chunk of your data allowance.
Why am I seeing this?
ZIP Extractor uses browser APIs to detect your connection type. This warning appears when a cellular or metered connection is detected and the file you're opening is larger than 10 MB. It doesn't show on desktop or on Wi-Fi.
What you can do
Download Full ZIP. If you're on Wi-Fi or have an unlimited data plan, click the "Download Full ZIP" button to proceed normally.
Wait for Wi-Fi. Close the file and reopen it when you're connected to a Wi-Fi network to avoid using cellular data.
Check your connection. If you believe this warning is incorrect (for example, you're on Wi-Fi but the browser reported otherwise), you can safely proceed by clicking "Download Full ZIP".
Technical details
This feature uses the Network Information API (navigator.connection) available in Chromium-based browsers (Chrome, Edge, Samsung Internet). It checks the type, effectiveType, and saveData properties. On browsers that don't support this API (Safari, Firefox), the warning doesn't appear.
Your browser ran out of memory while saving a file from the archive to your device. When extracting to your computer, ZIP Extractor decompresses each file in memory before writing it to disk. If a file is large enough to exceed the browser's per-tab memory limit, the write fails.
What you can do
Close other tabs and applications. Each open tab uses memory. Closing tabs you aren't using frees memory for ZIP Extractor.
Extract fewer files at once. Instead of extracting all files, select and extract a smaller batch at a time to reduce peak memory usage.
Extract to Google Drive instead. Uploading files to Drive uses less browser memory than writing to your local file system. Choose the "Extract to Drive" option instead of extracting to your computer.
Try a different browser. Some browsers allocate more memory per tab than others. Chrome and Edge typically handle larger files well.
Use a device with more RAM. If possible, try extracting on a desktop or laptop with at least 8 GB of RAM.
Why does this happen?
Web browsers put memory limits on each tab to keep the overall system stable. When extracting locally, the browser has to hold the decompressed file data in memory while writing it to disk. Large files, or many files extracted in a row, can push past the per-tab limit.
Your Google Drive storage quota is full. Files can't be uploaded to Drive until you free up space or upgrade your storage plan. Google Drive storage is shared across Drive, Gmail, and Google Photos, so deleting old emails or photos can also free up space.
What you can do
Manage your storage. Use the "Manage Storage" button to open your Google Drive storage page, which shows what's using space.
Delete files and empty the Trash. Deleted files still count against your quota until you empty the Trash. Open the Trash in Google Drive and click "Empty Trash."
Check Gmail and Google Photos. Large email attachments and photos stored at original quality also use Drive storage. Review and clean up these services to reclaim space.
Upgrade your storage plan. Visit Google One to purchase additional storage.
Extract to your computer instead. If you need the files immediately, use the "Extract to computer" option in ZIP Extractor to download files directly to your device rather than uploading to Drive.
ZIP Extractor was unable to save a file to your Google Drive. The file was decompressed successfully, but the upload didn't complete. This can happen when saving from either the preview or the file listing.
Common causes
Network disconnected. Your internet connection dropped during the upload. Check that you're online, then try again.
Google Drive storage full. Your Drive storage quota may be exceeded. Free up space or upgrade your storage plan, then try again.
Sign-in session expired or invalid. Your Google session may have timed out, or your account may not have permission to upload to Drive. Sign out and sign back in, then retry the save.
Temporary server error. Google Drive may be experiencing a temporary outage. Wait a moment and try again.
File too large. Very large files may time out before the upload completes. Try downloading the file instead and uploading it to Drive separately.
Upload session error. The server occasionally fails to initialize the upload session. If the error message references a "Session URI," try again. This is a transient server-side issue.
Rate limited or too many requests. Google Drive limits the number of requests per minute. Wait a moment and try again.
What you can do
Check your internet connection.
Click "Save to Drive" again to retry the upload.
Download the file instead. Use the Download button to save the file to your computer, then upload it to Google Drive manually.
ZIP Extractor can preview many common file types in your browser, but not every format is supported. When a file type can't be previewed, you'll see a "No preview available" message.
What you can do
Download the file. Click the Download button to save the file to your computer, then open it with the appropriate application.
Try "Preview as text." Some file types (configuration files, log files, scripts) are plain text with an uncommon extension. Click the Preview as text button to try displaying the file contents as text.
Extract to Google Drive. You can extract the file to your Google Drive and open it with a compatible Google Workspace app or connected third-party app.
Previewable file types
ZIP Extractor can preview these types in the browser:
Your browser was unable to play an audio or video file from the archive. The file may use a format or codec that your browser doesn't support.
What you can do
Download the file and open it locally. A dedicated media player like VLC supports nearly every format. Use the Download button to save the file, then open it with your preferred player.
Try a different browser. Browser codec support varies. Chrome and Edge support the widest range of formats. Firefox and Safari may not play certain codecs (for example, AAC in some containers, or HEVC/H.265).
Check if the file is corrupt. If the file was extracted from a damaged archive, it may be incomplete. Try re-downloading the original archive and extracting again.
Commonly supported formats
Most modern browsers support MP3, AAC, Ogg Vorbis, WAV, and FLAC for audio, and MP4 (H.264), WebM (VP8/VP9), and Ogg Theora for video. Formats like WMA, ALAC, AVI (non-H.264), and MKV may require a dedicated player.
Your browser was unable to display an image file from the archive. The browser didn't recognize the file as a supported image format.
What you can do
Download the file and open it locally. Use the Download button to save the file, then open it with an image viewer or editor on your computer. Desktop applications often support more formats than browsers do.
Check the file extension. The file may have an incorrect extension. For example, a file named photo.jpg might actually be a TIFF, BMP, or RAW file that the browser cannot display. Try renaming it with the correct extension and opening it in a dedicated image viewer.
Check if the file is corrupt. If the archive was damaged during download or transfer, individual files inside it may be incomplete or corrupted. Try re-downloading the original archive and extracting again.
Try a different browser. Browser image format support varies slightly. Chrome and Edge generally support the widest range of image formats.
Commonly supported image formats
Most modern browsers support JPEG, PNG, GIF, WebP, SVG, BMP, and ICO. Formats like TIFF, RAW (CR2, NEF, ARW), HEIC/HEIF (outside Safari), PSD, and AI typically require a dedicated image viewer or editor.
ZIP Extractor was unable to display the contents of a file as text. The file was extracted from the archive successfully, but the text couldn't be decoded or rendered in the preview.
Common causes
Unsupported text encoding. The file may use a character encoding that your browser doesn't support. ZIP Extractor tries to auto-detect the encoding, but some legacy or uncommon encodings (such as certain older Cyrillic or East Asian codepages) may not be recognized.
Binary file mistaken for text. If the file isn't actually a text file (for example, a renamed image, database, or compiled binary), trying to display it as text will fail or show garbled content.
Corrupted text data. The file contents may be damaged, resulting in byte sequences that cannot be decoded as valid text in any encoding.
What you can do
Try a different encoding. Use the Encoding button (or dropdown) to manually select a different character encoding. Common alternatives include Windows-1251 (Cyrillic), Shift_JIS (Japanese), Big5 (Chinese), and EUC-KR (Korean).
Download the file. Download the file to your computer and open it with a text editor that supports a wider range of encodings, such as VS Code, Notepad++, or Sublime Text.
Check the file type. Verify that the file is actually a text file. Files with extensions like .txt, .csv, .log, .xml, and .json are typically text. Other file types may not display correctly as text.
Technical details
ZIP Extractor uses the browser's built-in TextDecoder API to convert raw bytes into text. This API supports the encodings defined in the WHATWG Encoding Standard. When auto-detection (powered by jschardet) returns an encoding name that falls outside this set, ZIP Extractor translates it to the closest supported encoding. If no suitable translation exists, the preview will show an error.
This EPUB file is protected by Digital Rights Management (DRM) and can't be rendered in ZIP Extractor's built-in reader. DRM-protected EPUBs encrypt their content so that only authorized reading applications can open them.
What you can do
Open the EPUB in an authorized reader app. If you purchased this EPUB from an online bookstore (Apple Books, Kobo, Google Play Books, etc.), open it in that store's official reading app, which has the credentials to decrypt the content.
Download the file. You can still extract the EPUB from the archive and download it to your device. Use the file listing to select the EPUB file, then click Download.
Check if a DRM-free version is available. Some publishers offer DRM-free editions. Check the original source or contact the publisher.
Common DRM schemes
ZIP Extractor detects Apple FairPlay DRM and Adobe ADEPT DRM. These are the most common protection schemes used by major e-book retailers. Font obfuscation (used by many DRM-free EPUBs to protect embedded fonts) is not treated as DRM and doesn't trigger this error.
