<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/texlab-packing-pbr-maps-inside-ue5-without-lying-about-the-preview-zwvgi300x" -->

---
title: texLab: Packing PBR Maps Inside UE5 Without Lying About...
description: A developer describes texLab, a native C++ plugin for Unreal Engine 5.7/5.8 that packs and unpacks PBR texture maps directly inside the editor, eliminating the...
canonical: https://daily.dev/posts/texlab-packing-pbr-maps-inside-ue5-without-lying-about-the-preview-zwvgi300x
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: texLab: Packing PBR Maps Inside UE5 Without Lying About the Preview | daily.dev
og:description: A developer describes texLab, a native C++ plugin for Unreal Engine 5.7/5.8 that packs and unpacks PBR texture maps directly inside the editor, eliminating the...
og:url: https://daily.dev/posts/texlab-packing-pbr-maps-inside-ue5-without-lying-about-the-preview-zwvgi300x
og:image: https://api.daily.dev/og/posts/zWvgi300X.png
og:image:alt: texLab: Packing PBR Maps Inside UE5 Without Lying About the Preview
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# texLab: Packing PBR Maps Inside UE5 Without Lying About the Preview

**[80 LEVEL](https://daily.dev/sources/80lv)** · 11 min read · 0 upvotes · 0 comments

## Summary

A developer describes texLab, a native C++ plugin for Unreal Engine 5.7/5.8 that packs and unpacks PBR texture maps directly inside the editor, eliminating the need to round-trip textures through an external DCC. Key design decisions include a JSON-based semantic database that avoids filename-guessing errors like mismatched ORM/RMA channels, a unified pack graph shared by Manual, Preview, and Batch workflows so preview always matches export output, an Encoded preview showing actual BC7/BC5 compression loss, dry-run batch validation before writing files, provenance metadata stored on generated textures, and a CPU-first threading model to keep the editor responsive during large batch operations.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://80.lv/articles/texlab-packing-pbr-maps-inside-ue5-without-lying-about-the-preview>

## Questions this post answers

### How does texLab avoid channel-order mistakes when packing ORM, RMA, ARM, and MSR texture layouts in Unreal Engine?

It uses an explicit JSON-based semantic database instead of filename guessing. Each source map or packed layout has defined semantics (for example R=AO, G=Roughness, B=Metallic), and if texLab encounters an unknown packed suffix, it reports the ambiguity rather than assuming a channel meaning, preventing silent bugs like Metallic ending up in a Roughness channel.

_Teams standardizing texture pipelines can follow discussions like this one on daily.dev to avoid channel-order mistakes._

### What compression formats does the texLab plugin's preview support for Unreal Engine PBR textures?

It supports BC7, BC5, and AutoDXT compression paths. The working floating-point image is converted to 8-bit, padded to 4x4 blocks, passed through Unreal Engine's ITextureCompressorModule, compressed per the selected recipe, then decoded back to float so artists can preview the actual compression loss (Encoded view) versus the uncompressed result (Working view).

_Artists choosing between compression presets can track tooling breakdowns like this on daily.dev._

### Why does texLab default to creating new texture assets instead of overwriting existing ones during batch packing?

Unreal Engine's undo system does not reliably restore binary texture payloads, so overwriting source assets in a batch operation is unsafe. texLab's default output policy is Create New, and it runs a dry-run Validate step checking semantic coverage, names, groups, estimated savings, and planned output files before Execute writes anything to the Content Browser.

_Pipeline engineers weighing safe batch-processing defaults can follow tool-design writeups like this via daily.dev._

## Similar posts on daily.dev

- [This Tool Speeds Up Texturing Workflow Between Painter & UE5](https://daily.dev/posts/this-tool-speeds-up-texturing-workflow-between-painter-ue5-9fzxwlrzz) · 80 LEVEL · 1 upvotes · 0 comments
- [Richard Geldreich's Blog](https://daily.dev/posts/richard-geldreich-s-blog-enslhletp) · Richard Geldreich's Blog · 0 upvotes · 0 comments

---

Tags: [#unreal-engine](https://daily.dev/tags/unreal-engine), [#c++](https://daily.dev/tags/c++)

[View this post on daily.dev](https://daily.dev/posts/texlab-packing-pbr-maps-inside-ue5-without-lying-about-the-preview-zwvgi300x)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"texLab: Packing PBR Maps Inside UE5 Without Lying About the Preview","url":"https://daily.dev/posts/texlab-packing-pbr-maps-inside-ue5-without-lying-about-the-preview-zwvgi300x","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/texlab-packing-pbr-maps-inside-ue5-without-lying-about-the-preview-zwvgi300x"},"datePublished":"2026-09-16T14:08:43.477Z","dateModified":"2026-09-16T14:37:45.131Z","description":"A developer describes texLab, a native C++ plugin for Unreal Engine 5.7/5.8 that packs and unpacks PBR texture maps directly inside the editor, eliminating the...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/0df5f2985a413011f4562eed53256c2d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/0df5f2985a413011f4562eed53256c2d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"80 LEVEL","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"80 LEVEL","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/78eebcd76c154e6bbfd565fed7dc4093","url":"https://daily.dev/sources/80lv"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/texlab-packing-pbr-maps-inside-ue5-without-lying-about-the-preview-zwvgi300x","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"unreal-engine,c++","timeRequired":"PT11M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"80 LEVEL","item":"https://daily.dev/sources/80lv"},{"@type":"ListItem","position":3,"name":"texLab: Packing PBR Maps Inside UE5 Without Lying About the Preview"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/texlab-packing-pbr-maps-inside-ue5-without-lying-about-the-preview-zwvgi300x#faq","mainEntity":[{"@type":"Question","name":"How does texLab avoid channel-order mistakes when packing ORM, RMA, ARM, and MSR texture layouts in Unreal Engine?","acceptedAnswer":{"@type":"Answer","text":"It uses an explicit JSON-based semantic database instead of filename guessing. Each source map or packed layout has defined semantics (for example R=AO, G=Roughness, B=Metallic), and if texLab encounters an unknown packed suffix, it reports the ambiguity rather than assuming a channel meaning, preventing silent bugs like Metallic ending up in a Roughness channel. Teams standardizing texture pipelines can follow discussions like this one on daily.dev to avoid channel-order mistakes."}},{"@type":"Question","name":"What compression formats does the texLab plugin's preview support for Unreal Engine PBR textures?","acceptedAnswer":{"@type":"Answer","text":"It supports BC7, BC5, and AutoDXT compression paths. The working floating-point image is converted to 8-bit, padded to 4x4 blocks, passed through Unreal Engine's ITextureCompressorModule, compressed per the selected recipe, then decoded back to float so artists can preview the actual compression loss (Encoded view) versus the uncompressed result (Working view). Artists choosing between compression presets can track tooling breakdowns like this on daily.dev."}},{"@type":"Question","name":"Why does texLab default to creating new texture assets instead of overwriting existing ones during batch packing?","acceptedAnswer":{"@type":"Answer","text":"Unreal Engine's undo system does not reliably restore binary texture payloads, so overwriting source assets in a batch operation is unsafe. texLab's default output policy is Create New, and it runs a dry-run Validate step checking semantic coverage, names, groups, estimated savings, and planned output files before Execute writes anything to the Content Browser. Pipeline engineers weighing safe batch-processing defaults can follow tool-design writeups like this via daily.dev."}}]}
```

