What are the technical specs for minting an NFT?

Submit your artwork on Foundation following these guidelines

  • Main uploaded artwork: JPG, PNG, GIF, SVG or MP4, up to 50 MB. For still images, a ~3000 px width is ideal.

  • For video, 1080p or 4K is best.

  • Uploading a video that is larger than 2700px on either side will cause issues when loading on mobile


What are the causes of large video file sizes?


Length of video

  • A longer video will need more data


Video resolution e.g 720, 1080, 2k, 4k

  • The number of pixels that are used to create a frame of video, the more pixels the larger the file size


Framerate e.g 30fps, 60fps

  • The number of frames used per second of video, the higher the number the more frames are used, and therefore the larger the file size


Bitrate e.g 2mbps, 10mbps, 30mbps

  • This is the amount of video data that is processed for a second of footage, the higher bitrate the higher the amount of detail you will see in the video but also the higher the size of the video.

  • This is the main source of "bad looking" videos, where you see artifacts and blocking and tearing.


Codec e.g h264, AV1

  • This is the format that the video uses to encode the video information that makes it playable back on a number of devices. Most video codecs are lossy meaning when they are encoded they remove information from the original video footage that the codec determines will be unnoticeable to the viewer. Different codecs have different algorithms that affect the compression and eventual size and quality output.


How to create the best-looking content while keeping file size below 50MB

  • Once you have got your raw footage, you need to decide what resolution you want it to be in a suggestion is between 1080p & 2K but bear in mind you will need higher bitrates to make larger resolutions look sharp.


  • Next is framerate, either 30fps or 60fps will be fine, but remember higher framerates will add to increased file size.


  • Bitrate is the next and probably largest contributor to file size, a low bitrate can be seen in the final product as blocky/blurry footage. A maximum of bitrate should be 36mbps anything more will add significant file size to the output but will become perceptually lossless.


  • The final piece is the codec, if you want your original asset to be playable natively in current browsers you should use a codec & container format that is widely supported such as a WebM container using a VP8 video codec and Opus codec for audio or a MP4 container using a H.264 video codec with AAC as a audio codec.


  • To ensure playback on Foundation we generate extra assets by taking the source video and running it through a transcoder to generate guaranteed web playable assets. These assets are H264 code MP4 videos with AAC audio we cap bitrate to 36mbps. This does not affect the original asset at all these are copies for use within the application the original asset is stored immutably on ipfs.


If you would like to learn even more about Web video codecs this guide on MDN is very useful https://developer.mozilla.org/en-US/docs/Web/Media/Formats/Video_codecs

Was this article helpful?

116 out of 129 found this helpful

Have more questions? Submit a request

Articles in this section

See more