Convert GBR to HDR

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

GBR vs HDR Format Comparison

Aspect GBR (Source Format) HDR (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
HDR
Radiance RGBE (High Dynamic Range)

The Radiance HDR format (.hdr/.pic) was developed by Greg Ward for the Radiance lighting simulation system in the late 1980s. It stores high dynamic range image data using RGBE encoding (RGB + shared exponent), capturing a much wider range of light intensities than standard 8-bit images. HDR is widely used for environment maps, light probes, and image-based lighting in 3D rendering and architectural visualization.

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: RGBE (8-bit mantissa + 8-bit shared exponent)
Compression: Run-length encoding (RLE)
Transparency: Not supported (RGB only)
Animation: Not supported
Extensions: .hdr, .pic
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: Not supported (RGB only, no alpha)
  • Dynamic Range: Over 76 orders of magnitude
  • Color Space: Linear RGB with extended range
  • Encoding: RGBE shared-exponent for compact storage
  • HDR: Native HDR format — primary purpose
  • Metadata: Text header with exposure and format info
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
# ~/.config/GIMP/2.10/brushes/

HDR processing for lighting and rendering:

# Convert to HDR with ImageMagick
magick input.png output.hdr

# View HDR with tone mapping
magick output.hdr -evaluate Multiply 2 \
  tonemapped.png

# Use as environment map in Blender
# World → Environment Texture → .hdr file
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
  • Captures full dynamic range of light intensities
  • Compact RGBE encoding for HDR data
  • Standard format for 3D environment lighting
  • RLE compression reduces file size
  • Wide support in 3D renderers and game engines
  • Simple text header format easy to parse
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
  • No alpha channel support
  • Not viewable in web browsers
  • RGBE encoding can have precision issues in dark areas
  • Older format being supplanted by EXR in VFX
  • Limited to RGB color data only
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
  • Environment maps for image-based lighting
  • Light probe data for 3D scene illumination
  • Architectural visualization lighting
  • HDR panoramas for virtual reality backgrounds
  • Radiance lighting simulation input/output
Best For
  • GIMP digital painting and illustration workflows
  • Creating reusable brush libraries
  • Storing small pattern stamps with transparency
  • Artists working within the GIMP ecosystem
  • 3D rendering environment maps and light probes
  • Image-based lighting for photorealistic scenes
  • Architectural visualization with real-world lighting
  • HDR content for tone mapping workflows
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: ~1989 (Greg Ward, Radiance system)
Current Version: Radiance RGBE (#?RADIANCE)
Status: Mature, widely supported in 3D
Evolution: Original RGBE → RLE-compressed variant
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, GIMP, HDR Shop, Luminance HDR
3D Software: Blender, Maya, 3ds Max, Cinema 4D
Game Engines: Unity, Unreal Engine (skybox/IBL)
OS Preview: Limited (requires HDR viewer)
CLI Tools: Radiance tools, ImageMagick, Pillow

Why Convert GBR to HDR?

Converting GBR to HDR transforms GIMP brush patterns into Radiance high dynamic range format, enabling their use as texture elements in 3D rendering and lighting pipelines. The HDR format is the standard for environment maps and light probes used in image-based lighting (IBL), making this conversion valuable for 3D artists who want to use brush-created patterns in their rendering workflows.

Brush patterns can serve as custom light cookie textures, gobo patterns, or procedural elements when converted to HDR. In 3D rendering, these patterns modulate light intensity and create interesting shadow and illumination effects. The HDR format's extended dynamic range means the brush values can be scaled beyond the 0-1 range, creating light emission effects that are not possible with standard 8-bit formats.

For architectural visualization and product rendering, custom brush patterns in HDR format can be used as projection textures for spotlights, creating unique lighting patterns that add visual interest to rendered scenes. The RGBE encoding preserves the relative intensities of the brush pattern with high precision across the entire dynamic range.

Note that HDR format does not support alpha transparency — the alpha channel from RGBA GBR brushes is discarded during conversion. If transparency is important for your use case, consider EXR format instead, which supports both HDR and alpha channels. HDR is best when you specifically need Radiance-format files for lighting applications.

Key Benefits of Converting GBR to HDR:

  • 3D Rendering Compatible: Works with Blender, Maya, 3ds Max, and all major 3D tools
  • Light Cookie Textures: Use brush patterns to shape spotlight projections
  • Extended Dynamic Range: Values can exceed 1.0 for light emission effects
  • Game Engine Support: Unity and Unreal accept HDR for skyboxes and IBL
  • Compact Encoding: RGBE with RLE compression keeps files manageable
  • Industry Standard: Widely supported format for HDR image data
  • Lighting Simulation: Compatible with Radiance ray-tracing system

Practical Examples

Example 1: Custom Light Cookie for 3D Spotlight

Scenario: A 3D artist creates a decorative pattern brush in GIMP to use as a spotlight cookie texture in Blender, projecting the pattern as a light shadow.

Source: leaf_shadow.gbr (256x256px, grayscale, 65 KB)
Conversion: GBR → HDR (RGBE encoded)
Result: leaf_shadow.hdr (256x256px, ~95 KB)

Blender workflow:
✓ HDR texture assigned to spotlight's cookie parameter
✓ Leaf pattern projects as dappled shadow on surfaces
✓ Dynamic range allows varying light intensity across pattern
✓ Renders naturally with path tracing
✓ Creates organic, hand-crafted lighting effects

Example 2: Procedural Element for Environment Lighting

Scenario: A visualization artist uses GIMP brush patterns as custom elements in a composite HDR environment map for architectural rendering.

Source: cloud_brush.gbr (512x512px, RGBA, 1 MB)
Conversion: GBR → HDR (RGBE with RLE)
Result: cloud_brush.hdr (512x512px, ~380 KB)

Visualization workflow:
✓ Cloud pattern composited into HDR sky environment
✓ HDR values drive realistic sky illumination
✓ Pattern integrates with IBL lighting system
✓ Scalable intensity for different lighting moods
✓ Unique sky look for each visualization project

Example 3: Game Engine Lightmap Textures

Scenario: A game developer creates custom lightmap detail patterns as GIMP brushes for enhancing baked lighting quality in a Unity game scene.

Source: light_caustic.gbr (128x128px, grayscale, 16 KB)
Conversion: GBR → HDR (RGBE format)
Result: light_caustic.hdr (128x128px, ~24 KB)

Game lighting benefits:
✓ HDR format preserves light intensity variations
✓ Caustic pattern used as lightmap detail overlay
✓ Unity accepts HDR textures for lighting data
✓ Extended range allows realistic bright spots
✓ Adds visual complexity to baked lighting

Frequently Asked Questions (FAQ)

Q: What happens to the brush alpha channel in HDR?

A: HDR (Radiance RGBE) format does not support alpha channels. The transparency data from RGBA GBR brushes is discarded during conversion, and the output contains only RGB color data. If you need both HDR dynamic range and alpha transparency, use OpenEXR format instead.

Q: Can I view HDR files on my computer?

A: Standard image viewers typically cannot display HDR files properly. You can view them in GIMP, Photoshop, Blender, or dedicated HDR viewers like HDR Shop or Luminance HDR. The image will appear with tone mapping applied to fit the display's standard dynamic range.

Q: How does HDR compare to EXR?

A: Both store high dynamic range data, but they differ in capabilities. EXR supports alpha channels, arbitrary named channels, multiple compression methods, and higher precision (32-bit float). HDR uses the simpler RGBE encoding with RGB-only data. HDR is more compact and widely used for environment maps; EXR is preferred for VFX compositing.

Q: Will a brush pattern benefit from HDR dynamic range?

A: GBR brushes are 8-bit, so the conversion does not add new dynamic range information. However, storing in HDR format allows the values to be scaled and processed in HDR pipelines without clamping or precision loss. Values can be multiplied above 1.0 in rendering to create light emission effects, which is not possible with 8-bit formats.

Q: Can I use HDR files in Blender?

A: Yes, Blender fully supports Radiance HDR files. They can be used as environment textures for world lighting, as texture inputs for material nodes, and as light cookie patterns. Blender reads HDR natively and processes the data in its internal float-precision color pipeline.

Q: How large are the resulting HDR files?

A: HDR files use RGBE encoding (4 bytes per pixel) with RLE compression. A 256x256 brush produces an HDR file of approximately 80-120 KB, depending on content complexity. This is comparable to the raw GBR size but with the advantage of HDR-capable encoding.

Q: Is HDR suitable for web use?

A: No, HDR files are not supported by web browsers and cannot be displayed on websites. The format is designed for 3D rendering, lighting simulation, and professional image processing applications. For web use, convert your brush patterns to PNG, WebP, or AVIF instead.

Q: What is RGBE encoding?

A: RGBE stands for Red, Green, Blue, Exponent. It stores each pixel as three 8-bit mantissa values (one per color channel) plus a shared 8-bit exponent. This allows representing a massive range of brightness values (from very dark to very bright) in just 4 bytes per pixel, much more efficiently than full 32-bit floating point per channel.