GTA V .ytd Texture Optimization Explained: Resolution, Formats and 3 Methods

What is inside a .ytd, why modded vehicle textures are oversized, which resolution and DXT format each surface needs, and three ways to shrink them: in the browser, in batch on your PC, or by hand in OpenIV.

Updated 6 min read11 sections

Have a .ytd that is too large? The Texture Optimizer shrinks it in your browser; the file is not uploaded. Open the Texture Optimizer

What This Guide Covers

A .ytd is a texture dictionary, and on most modded servers these files are the bulk of what players download. This guide explains what is inside one, why modded vehicle textures are so large, which resolution and compression format each surface needs, and the three ways to shrink them.

Note

Just want to shrink a file right now? Follow the in-browser Texture Optimizer tutorial instead. It needs no install.

What Are .ytd Files?

YTD stands for Y Texture Dictionary, GTA V's container format for textures. Every vehicle, building, prop and character uses one or more. A vehicle's dictionary holds its paint, interior, lights, badges and liveries as individual textures, each stored with a chain of progressively smaller copies called mipmaps. The wiki has the short definition: .ytd texture dictionary.

In a modded vehicle resource the dictionary is usually the largest file, often 10-50 MB, because many mod authors ship every texture at the resolution they authored it in.

Why Optimize Textures?

The Problem

A typical showroom-quality vehicle mod includes textures at 4096x4096. At that size:

  • One vehicle's textures can be 20-50 MB
  • 50 such vehicles is 1-2.5 GB in textures alone
  • Players get long loading times and texture pop-in
  • Any asset above FiveM's 16 MiB warning may not load reliably: see the "16 MB limit" explained

The Reality

In game, most vehicle textures are seen at a distance where 4096x4096 and 1024x1024 look identical. Even up close, 2048x2048 is enough for most surfaces. The extra resolution is data nobody sees.

FiveM itself works on that assumption. The client setting str_maxVehicleTextureRes "limits the maximum resolution of vehicle textures" and defaults to 1024 (FiveM console commands), so a default client does not show a vehicle's 4K level at all. The limit works by picking a smaller mipmap, which is one more reason every texture should keep its mip chain: a texture saved without mipmaps has no smaller level to fall back to.

Resolution and Format: Where the Size Comes From

Two settings decide how big a texture is: its resolution and its compression format.

Resolution. Halving the width and height quarters the size. A 4096 px texture is 4 times the size of a 2048 px one and 16 times the size of a 1024 px one.

Format. Uncompressed textures store 4 bytes per pixel. DXT1 stores half a byte per pixel and DXT5 one byte per pixel, so compressing an uncompressed texture cuts it to an eighth or a quarter before you touch the resolution. Use DXT1 when the texture has no transparency and DXT5 when it does.

SurfaceSensible resolutionFormat
Body paint, liveries with text2048 pxDXT1, or DXT5 with alpha
Interior, dashboard, seats1024 pxDXT1
Engine bay, underside, boot1024 px or 512 pxDXT1
Badges, lights, small details512 pxDXT5 where transparent
Glass, decals512 px to 1024 pxDXT5

Method 1: In the Browser (One Resource)

The Texture Optimizer runs entirely in your browser. It removes the top mip levels of each texture so the smaller copy already stored in the file becomes the new top level. No pixels are re-encoded, and nothing is uploaded.

  • Free: one file at 1024 px
  • Unlimited ($15 one-time): 2048, 1024 or 512 px, and a whole resource zip rebuilt in one go

Best for: fixing the one or two oversized files the Resource Inspector flagged in a resource. The steps are in how to optimize .ytd textures in your browser.

Method 2: Glory Optimizer (Whole Folders)

Glory Optimizer is a Windows desktop app for batch work: point it at a folder and it processes every .ytd inside.

How to Use It

  1. Download and install Glory Optimizer
  2. Select your Textures Folder, the folder containing .ytd files
  3. Set a Backup Folder (optional but recommended); your originals are copied here first
  4. Set the Optimize Size, the threshold in pixels. Textures where width + height is at or above this value are downsized. Default is 1024.
  5. Click Optimize and wait for it to finish
  6. Check the before/after stats to see how much space was saved

Choosing the Right Optimize Size

  • 4096: very conservative. Only downsizes the largest textures.
  • 2048: a good balance. Catches most oversized textures.
  • 1024: the recommended default for vehicles.
  • 512: aggressive. Some textures will look softer up close.

Best for: an existing server with dozens of unoptimized resources. It is $10 one-time, or part of the $20 Complete Bundle.

Method 3: Manual Optimization in OpenIV

Tools Needed

  • OpenIV to open and edit .ytd files
  • An image editor (Photoshop, GIMP, Paint.NET) to resize textures
  • A DDS exporter to save with DXT compression

Manual Steps

  1. Open the .ytd file in OpenIV
  2. Export each oversized texture as .dds or .png
  3. Resize in your image editor (for example 4096x4096 to 1024x1024)
  4. Save as DDS with DXT1 (no alpha) or DXT5 (with alpha), with mipmaps
  5. Import back into the .ytd
  6. Save and test

Allow several minutes per texture. A single vehicle can have 10-30 textures, so this is realistic for one special car and not for a whole server. Its advantage is control: you decide texture by texture, and it is the only method here that lets you change a texture's format.

Which Method?

Browser optimizerGlory OptimizerManual
Works onOne resource or a few filesWhole foldersOne texture at a time
InstallNoneWindows appOpenIV plus an image editor
CostFree for one file, more with Unlimited$10 one-timeFree

Best Practices

Always Keep Backups

Before optimizing, back up your originals. Glory Optimizer has a built-in backup option; with the other methods, copy the folder first.

Test After Optimizing

Load the server and look at the vehicles:

  • Do textures look right from normal gameplay distance?
  • Is anything obviously blurry or broken up close?
  • Are liveries and text still readable?

Optimize in Batches

  1. Start with the largest .ytd files (biggest savings)
  2. Test after each batch
  3. If something looks wrong, restore from backup and use a higher resolution for that file

Skip Small Files

Files under 2 MB are already small. Focus on files over 5-10 MB.

When NOT to Optimize

  • Livery textures with fine text or logos can become unreadable at lower resolutions
  • UI and HUD textures need to stay pixel-exact
  • Map textures seen up close, such as building facades and signs

Optimize Your Textures Automatically

Glory Optimizer batch-resizes whole folders of .ytd files on your PC. $10 one-time. For a single file, the in-browser Texture Optimizer is free.

Have a gta5-mods.com link ready?

Paste it into the converter and download a FiveM resource with the stream folder, meta files and fxmanifest.lua in place.

  • 3 conversions free, no account needed
  • 2 more free if you leave an email
  • After that: $15 once for unlimited conversions and the Pro tools. No subscription, 14-day refund policy