Convert GBR to DDS

Drag and drop files here or click to select.
Max file size 100mb.
Uploading progress:

GBR vs DDS Format Comparison

Aspect GBR (Source Format) DDS (Target Format)
Format Overview
GBR
GIMP Brush Format

A specialized image format created by the GIMP project (GNU Image Manipulation Program) for storing custom brush tip patterns. GBR files contain a single raster image used as a stamp pattern when painting in GIMP. The format supports both grayscale brushes (version 1) and full RGBA color brushes (version 2), allowing artists to create detailed, reusable brush shapes with transparency information.

Lossless Standard
DDS
DirectDraw Surface

A container format developed by Microsoft for storing textures and environments used by DirectX graphics applications. DDS supports multiple compression methods (DXT1-5, BC1-7), mipmaps, cube maps, volume textures, and texture arrays. It is the standard texture format for game engines including Unity, Unreal Engine, and most DirectX-based applications, designed for direct GPU upload without CPU-side decompression.

Standard Lossless
Technical Specifications
Color Depth: 8-bit grayscale or 8-bit RGBA
Compression: Uncompressed raw pixel data
Transparency: Full alpha channel (version 2)
Animation: Not supported
Extensions: .gbr
Color Depth: Various (DXT1 to BC7, 4-8 bpp compressed)
Compression: DXT/BCn GPU-native block compression
Transparency: 1-bit (DXT1) or full alpha (DXT5/BC7)
Animation: Not supported (but supports texture arrays)
Extensions: .dds
Image Features
  • Transparency: Full alpha in version 2 RGBA brushes
  • Animation: Not supported
  • Metadata: Brush name and spacing stored in header
  • Color Modes: Grayscale (v1) and RGBA (v2)
  • HDR: Not supported (8-bit only)
  • Multi-resolution: Single resolution per file
  • Transparency: Full alpha channel with DXT5 or BC7
  • Mipmaps: Full mipmap chain for level-of-detail
  • Cube Maps: 6-face environment maps
  • Volume Textures: 3D texture data support
  • HDR: BC6H supports HDR textures
  • GPU Native: Direct upload to GPU memory
Processing & Tools

GBR files are natively handled by GIMP:

# GBR brush structure
# Header: size(4) + version(4) + width(4)
#   + height(4) + bpp(4) + name(null-term)
# Data: raw pixel data (grayscale or RGBA)

# GIMP brushes directory location
# ~/.config/GIMP/2.10/brushes/

DDS texture creation and compression:

# Convert to DDS with ImageMagick
magick input.png -define dds:compression=dxt5 \
  output.dds

# NVIDIA Texture Tools
nvcompress -bc3 input.png output.dds

# Python with Pillow (uncompressed DDS)
from PIL import Image
img.save("output.dds")
Advantages
  • Native GIMP brush format with full editor integration
  • Supports transparency for precise brush shapes
  • Simple binary format easy to parse programmatically
  • Lossless storage preserves exact brush detail
  • Embedded brush metadata (name, spacing)
  • Lightweight files for small brush patterns
  • GPU-native compression for instant texture rendering
  • Built-in mipmap chain for multi-resolution display
  • Industry-standard game texture format
  • Supports cube maps and volume textures
  • Multiple compression modes for different quality needs
  • Direct support in Unity, Unreal, and DirectX engines
Disadvantages
  • Only usable within GIMP ecosystem
  • No compression results in larger files for big brushes
  • Not viewable in web browsers or standard image viewers
  • Limited to 8-bit color depth
  • No standard metadata beyond brush name and spacing
  • DXT compression is lossy (block artifacts on sharp edges)
  • Power-of-two dimensions recommended for GPU efficiency
  • Not suitable for web delivery or general viewing
  • Complex format with many variants
  • Limited support in standard image viewers
Common Uses
  • Custom brush tips in GIMP
  • Artistic texture stamps for digital painting
  • Repeating pattern brushes for illustration
  • Sharing brush collections among GIMP users
  • Specialized brush shapes for photo retouching
  • Game engine textures (Unity, Unreal Engine)
  • 3D model surface textures and materials
  • Environment maps and skyboxes
  • UI textures in DirectX applications
  • Normal maps and specular maps for 3D rendering
Best For
  • GIMP digital painting and illustration workflows
  • Creating reusable brush libraries
  • Storing small pattern stamps with transparency
  • Artists working within the GIMP ecosystem
  • Game development texture pipelines
  • Real-time 3D rendering applications
  • GPU-optimized texture storage
  • DirectX and OpenGL graphics applications
Version History
Introduced: 1995 (GIMP 0.54)
Current Version: Version 2 (RGBA support)
Status: Stable, maintained by GIMP project
Evolution: v1 (grayscale) → v2 (RGBA color)
Introduced: 1999 (DirectX 7)
Current Version: DDS with DX10 header extension
Status: Industry standard for game textures
Evolution: DXT1-5 (1999) → BC1-5 (2006) → BC6H/BC7 (2009)
Software Support
Image Editors: GIMP (native), limited third-party support
Web Browsers: Not supported
OS Preview: Not natively supported
Mobile: Not supported
CLI Tools: GIMP Script-Fu, Python with custom parser
Image Editors: Photoshop (NVIDIA plugin), GIMP (plugin)
Web Browsers: Not supported
OS Preview: Windows (with codec), limited on macOS/Linux
Game Engines: Unity, Unreal Engine, Godot, CryEngine
CLI Tools: NVIDIA Texture Tools, Pillow, ImageMagick

Why Convert GBR to DDS?

Converting GBR to DDS transforms GIMP brush patterns into GPU-ready game textures that can be loaded directly by game engines like Unity, Unreal Engine, and any DirectX-based application. This conversion bridges the gap between artistic brush creation in GIMP and real-time 3D rendering, allowing artists to repurpose detailed brush patterns as in-game textures, particle effects, or UI elements.

DDS (DirectDraw Surface) is the industry standard for game texture storage because it supports GPU-native compression formats (DXT/BCn) that can be uploaded directly to video memory without CPU-side decompression. This means brush patterns converted to DDS load faster and use less GPU memory than uncompressed formats. For game developers, this translates to better performance and shorter loading times.

Brush patterns often make excellent game textures — organic patterns like paint splatters, watercolor washes, smoke effects, and natural textures that start as GBR brushes can be used as decal textures, particle sprites, terrain blending masks, or material details in 3D scenes. The conversion preserves the brush's visual characteristics while repackaging them for real-time rendering.

The DDS format also supports mipmaps, which are pre-computed lower-resolution versions of the texture used when objects are viewed at a distance. This prevents aliasing artifacts and improves rendering quality. The conversion process generates these mipmap levels automatically from the original brush data, creating a complete texture asset ready for engine import.

Key Benefits of Converting GBR to DDS:

  • Game Engine Ready: DDS textures load directly into Unity, Unreal, and other engines
  • GPU Optimized: Block compression allows direct GPU upload without decompression
  • Mipmap Support: Automatic level-of-detail for smooth rendering at all distances
  • Alpha Channel: Preserve brush transparency for particle effects and decals
  • Industry Standard: Universal game development texture format
  • Performance: Compressed DDS textures use less GPU memory than raw formats
  • Versatile: Use brush patterns as textures, sprites, masks, or UI elements

Practical Examples

Example 1: Creating Game Particle Effect Textures

Scenario: A game artist designs smoke and fire particle effects as GIMP brushes and needs them as DDS textures for a Unity particle system.

Source: smoke_puff.gbr (128x128px, RGBA, 65 KB)
Conversion: GBR → DDS (with alpha, mipmaps)
Result: smoke_puff.dds (128x128px, ~22 KB with DXT5)

Game development workflow:
✓ DDS texture imports directly into Unity as sprite
✓ Alpha channel creates soft smoke edges for blending
✓ DXT5 compression preserves alpha quality
✓ Mipmaps prevent aliasing at distance
✓ Multiple brush variants create varied particle effects

Example 2: Terrain Detail Textures for Open-World Games

Scenario: A terrain artist paints ground textures in GIMP using custom brushes and wants to use these patterns as terrain detail layers in Unreal Engine.

Source: grass_detail.gbr (256x256px, RGBA, 262 KB)
Conversion: GBR → DDS (DXT5 with mipmaps)
Result: grass_detail.dds (256x256px, ~44 KB)

Terrain workflow:
✓ Tiling brush pattern works as repeating ground texture
✓ GPU compression keeps terrain memory budget manageable
✓ Mipmap chain prevents texture swimming at angles
✓ Alpha channel used for terrain blending mask
✓ Import directly into Unreal landscape material

Example 3: Custom Decal Textures for 3D Scenes

Scenario: An environment artist creates weathering and damage decals as GIMP brushes for applying to 3D building surfaces in a game engine.

Source: rust_stain.gbr (512x512px, RGBA, 1 MB)
Conversion: GBR → DDS (DXT5 with full mipmap chain)
Result: rust_stain.dds (512x512px, ~175 KB)

Decal system benefits:
✓ Brush shape defines decal projection area via alpha
✓ DDS format supported by all decal projection systems
✓ 83% file size reduction vs raw pixel data
✓ Mipmaps ensure crisp detail at all viewing distances
✓ Multiple brush decals add variety to scene weathering

Frequently Asked Questions (FAQ)

Q: What compression does the output DDS use?

A: The conversion produces DDS files using standard compression supported by Pillow. For most use cases, the output is suitable for direct use in game engines. If you need specific DXT/BCn compression modes, you can use NVIDIA Texture Tools or texconv to recompress the DDS file after conversion.

Q: Do I need power-of-two dimensions?

A: While DDS technically supports non-power-of-two sizes, most game engines and GPUs perform best with power-of-two dimensions (64, 128, 256, 512, 1024). If your GBR brush is a non-standard size, consider creating it at a power-of-two resolution for optimal game engine compatibility.

Q: Will the brush alpha channel be preserved in DDS?

A: Yes, DDS supports alpha channels through various compression modes (DXT3, DXT5, BC7). The conversion preserves the GBR brush's transparency information, which is essential for particle effects, decals, and overlay textures in game engines.

Q: Can I use the converted DDS in Unity?

A: Yes, Unity supports DDS texture import. Simply place the converted DDS file in your Unity project's Assets folder, and Unity will recognize it as a texture. You can then adjust import settings (filter mode, wrap mode, compression) in the Unity Inspector.

Q: How does DDS file size compare to GBR?

A: With DXT5 compression, DDS files are typically 4-8x smaller than the raw pixel data in GBR. A 256x256 RGBA GBR brush (~262 KB) would compress to approximately 44-88 KB as DDS. The trade-off is minor quality reduction from the lossy block compression, which is generally imperceptible for brush-type imagery.

Q: Can grayscale GBR brushes be converted to DDS?

A: Yes, grayscale GBR brushes are converted to DDS. The grayscale data is typically stored as a single-channel or RGB texture depending on the DDS compression mode. Grayscale textures are commonly used as height maps, roughness maps, or mask textures in game material systems.

Q: Are mipmaps included in the output DDS?

A: The DDS format supports mipmaps, and they may be generated depending on the encoding process. Mipmaps are pre-computed lower-resolution versions of the texture that improve rendering quality and performance. If mipmaps are not included, game engines like Unity and Unreal can generate them on import.

Q: What is the best use case for GBR to DDS conversion?

A: The best use case is creating game textures from artistic brush patterns — particle effects, terrain details, decals, and UI elements. Artists who design in GIMP can use this conversion to bring their brush artwork directly into game development pipelines without intermediate format steps.