Are there ideal dimensions (width and height) for texture files?

You can use as many texture map files as you'd like, but for best performance we recommend configuring your software to output large 16K or 32K textures, whenever possible. Using multiple smaller textures (e.g. 2K, 4K, or 8K) results in more files, which will take longer to load and may not produce the best quality textures.

Texture width and height dimensions should always be a power of two.

• Here are several examples of correct power of two texture width and height dimensions:
  • 1024 x 1024 (1K)
  • 2048 x 2048 (2K)
  • 4096 x 4096 (4K)
  • 8192 x 8192 (8K)
  • 16384 x 16384 (16K)
  • 32768 x 32768 (32K)
  • 16384 x 4096 (Different width and height is fine, as long as they are both a power of two)

Automatic texture upscaling

Any texture image with a width or height that is not a power of two will automatically be upscaled to the next highest power of two. For example, a 17,000 x 17,000 texture will be upscaled to 32,768 x 32,768. This upscaling increases the amount of texture data our servers need to store and load, which can affect the cost of hosting the asset. For this reason, it's recommended to configure your application to generate and export power-of-two textures. Most applications do this by default.

For reference, the following list shows the size of each texture file measured in Gigapixels (GP):

• 32768 x 32768 (32K) = 1 GP
• 16384 x 16384 (16K) = 0.25 GP
• 8192 x 8192 (8K) = 0.06 GP
• 4096 x 4096 (4K) = 0.03 GP
• 2048 x 2048 (2K) = 0.008 GP
• 1024 x 1024 (1K) = 0.00211 GP

Nira supports an unlimited number of textures, and you can mix textures of different sizes within the same asset. For example, you could include 50 textures at 32K resolution (50 GP) along with 100 textures at 16K resolution (25 GP) in a single asset, totaling 75 GP.