OpenSea's current tools accept images (JPG, PNG, GIF, SVG), video (MP4 with H.264 video and AAC audio, up to 60 fps), and audio (MP3, WAV, FLAC), with size limits varying by upload type, but the most common silent failure is uploading an MP4 with H.265/HEVC video or MP3 audio tracks, which the pipeline rejects without a clear error.
Opensea lazy minting image formats and limits
OpenSea lazy minting accepts JPG, PNG, GIF, and SVG files. Each image file must be under 50 MB for single item uploads. Size limits vary by upload type: 50 MB for single items and 5 GB for Drops. If your PNG or animated GIF exceeds 50 MB for a single item upload, the upload will fail silently. The preview will not generate and you will not see a specific error in the browser. Do not upload TIFF, BMP, WEBP, or HEIC files. Renaming them to .jpg or .png will not work. The 50 MB limit for single items is checked before any codec analysis. A 51 MB GIF will be rejected before the format is even verified. When you create a collection in OpenSea Studio, click 'Create new' and select 'Collection or item' or 'Drop.' The file picker will accept any file extension. Only these four image types will actually process through the pipeline.
Video codecs and frame rate requirements
Use MP4 as your video container. It must use H.264 video codec with AAC audio. The most frequent silent failure occurs when your MP4 uses H.265/HEVC. This is a common export setting in modern video editors and screen recorders. The lazy minting pipeline cannot decode H.265. The upload will appear to complete but the NFT preview will remain blank. Set your frame rate to 60 fps or lower. Any file recorded at 120 fps or variable frame rates above 60 fps will fail during transcoding. Ensure audio within the MP4 is AAC. If your video contains an MP3 audio track, the pipeline will reject it without a warning. OpenSea does not support WebM, MKV, MOV, or AVI containers under any circumstances. When you export from Adobe Premiere or DaVinci Resolve, choose "H.264" under video codec and "AAC" under audio codec. Set frame rate to 30 or 60 fps to guarantee compatibility. If you later swap the source file, be aware that NFT metadata changing the file after lazy minting can break the token's on-chain reference permanently. This will save you from wasted gas fees on failed uploads.
Audio format support and the MP3 trap
For audio-only mints, upload MP3, WAV, or FLAC files. Each must be under 50 MB for single item uploads. Avoid the "MP3 trap." If you upload an MP4 file that contains only audio with an MP3 audio track instead of AAC, the pipeline will reject it. The container is MP4 but the codec is unsupported. Upload a pure MP3 file with the .mp3 extension instead. Use uncompressed PCM for WAV files. Compressed WAV variants like WAV with ADPCM or GSM codecs are not supported. Make sure FLAC files are standard 16-bit or 24-bit. 32-bit float FLAC files will fail. Before you mint an audio NFT, always check the file's actual codec using a tool like MediaInfo or ffprobe. Renaming a .wav file to .mp3 will not change the underlying codec and the pipeline will reject it.
When the answer is no
Do not upload WebM, MKV, MOV, AVI, TIFF, BMP, WEBP, HEIC, or PSD files. OpenSea lazy minting definitively rejects them regardless of file size. Do not use H.265/HEVC video in any container. Renaming a .webm file to .mp4 will not work. The pipeline inspects the actual binary header, not the extension. Do not upload an MP4 file with H.264 video but MP3 audio. The 50 MB limit for single items is applied before codec checks. A MOV file will still fail because the container is not supported. To avoid wasted time, always verify your file's codec and container using a free tool before uploading to the lazy minting collection form. Test with a small version of your file. This is the only reliable method to confirm compatibility. If you want to mint an NFT for free, you must adhere to these exact specs. Any deviation will cause the upload to fail during the collection creation step with no error message explaining why your file was rejected. Since a successful upload doesn't guarantee the metadata is on-chain, you should also verify a lazy minted NFT is actually on-chain before it sells to ensure your asset is permanently secured.
The platform does not provide a pre-upload validator, so testing with a small version of your file is the only reliable method to confirm compatibility.
