Drop the pack folder into your server's resources/ directory, then add ensure pack_name to your server.cfg and restart. The props are now loaded on your server.

One important step left: open your account page, find your pack, then copy the furniture entries shown in the pack popup and paste them into your own housing or spawn script. Without this, the props exist on the server but they will not appear in any in-game menu, so players can never place them.

Your packs are delivered to your Cfx account, not on Tebex. Go to portal.cfx.re, log in, and download your assets from your "Granted Assets" page. Need a step-by-step? Check the official Cfx walkthrough.

Nitro Booster packs are not store purchases. They are unlocked when you boost our Discord server, so they are not delivered through the Cfx portal like a normal pack.

To download them, you first need an active boost on our Discord server. Once your boost is active, log in to the site with that same Discord account and open your account page. Your unlocked Nitro Booster packs are available to download directly from there.

This access is tied to your boost. If you remove your boost from the Discord server, you lose access to the Nitro Booster packs.

Each purchase covers one FiveM server. You can transfer ownership of your pack directly from your Cfx portal, but be careful: once a transfer is done, it is permanent and cannot be reversed. The pack is gone from your account forever.

No. All Skrl 3D packs are protected with FiveM's Asset Escrow system to prevent leaks and unauthorized resale. The pack works exactly the same on your server: you install it, the props show up, players see them in game. The underlying files stay encrypted and cannot be copied or re-uploaded elsewhere. It protects your purchase and our work. Want the technical details? Read the official Asset Escrow FAQ.

Yes. Our props use valid model names, so any system that lets you place objects by model name can use them. Once the pack is started on your server, the props are available everywhere as native props.

Digital goods are non-refundable once delivered, except in cases covered by Tebex's policy. If you have a problem with a pack, reach out on Discord first. We always try to fix it before considering a refund.

No, and this is a common misunderstanding. The number of folders or resources on your server has no effect on performance. You can run 500 separate folders, it changes nothing. Asking a designer to pack several packs into a single resource does not optimize anything: it only makes the pack harder to update, harder to maintain, and heavier to load all at once.

What actually matters is the quality of the assets themselves. For real performance, the Lua scripts, the MLOs and the props (and above all their textures) must be properly optimized. One well-optimized pack in its own folder will always run better than ten poorly-optimized packs merged together. Focus on optimized assets, not on the folder count.

GTA's engine was not built for ultra high resolution textures. Most props are designed around 512x512 textures, and 1024x1024 is the realistic maximum for large or very detailed pieces. Always stick to power of two sizes (128, 256, 512, 1024).

Why not 2K or 4K? Every texture has to load into your graphics card memory (VRAM). GTA streams assets in real time with a limited memory budget, so oversized textures cause blurry surfaces, texture pop-in, stutter and FPS drops, especially for players on weaker hardware. A pack full of 4K textures also becomes huge and slow to download.

How to reduce the size? Resize your source image down to 512 or 1024 before converting, apply YTD compression (DXT1 when there is no transparency, DXT5 when there is), and generate mipmaps for clean rendering at distance. Drop any unused alpha channel. In game the result looks almost identical while staying light.

A YTD is a texture dictionary, basically one file that holds all the textures used by a model. To open or change what is inside, you need OpenIV, the free editing tool for GTA files.

To swap a texture: install OpenIV, enable Edit mode, then open your YTD file. It lists every texture in the dictionary. Select the one you want to change, click Replace, and import your new image. Keep the same resolution and format as the original (power of two, DXT compressed), then save the YTD.

XnConvert is a free image tool that does everything you need to prepare textures. It converts images to DDS and many other formats, resizes and resamples them, and ships with a full set of editing tools.

Before importing a texture into a YTD, use XnConvert to resize your image to a power of two size (512 or 1024) and export it as DDS with DXT compression. It works in batch, so you can prepare a whole set of textures in one pass, and it is completely free.

GTA's engine reserves fixed memory pools for each type of asset. The TxdStore is the pool that holds texture dictionaries, the YTD files. Every addon that ships textures loads them into this pool: prop packs, MLOs, custom vehicles, clothing and more.

When you run a lot of texture content at once, the default TxdStore pool fills up. If it goes over its limit, your server crashes. Before that point you usually see missing or blank textures and console errors, which are the warning signs that the pool is almost full.

The fix is to raise the ceiling. Add increase_pool_size "TxdStore" 26000 to your server.cfg. This tells the engine to reserve space for up to 26000 texture dictionaries, which covers most heavily modded servers.

Remember that 26000 is still a limit. It sets how many texture dictionaries your server can load at once, and everything counts: prop packs, MLOs, custom vehicles and clothing all add to it. If your server reaches that number, the next addon pushes past the limit and the crash comes back. At that point you need to remove some content or use lighter versions that rely on fewer textures.

The TxdStore is not the only pool that can overflow. The engine keeps a pool for almost every type of asset, and each one has a maximum value it can be raised to. When a heavily modded server crashes, raising these pools in your server.cfg usually fixes it.

# Pool Size Settings
increase_pool_size "CMoveObject" 75               # Max: 75
increase_pool_size "FragmentStore" 14000          # Max: 14000
increase_pool_size "OcclusionInteriorInfo" 20     # Max: 20
increase_pool_size "OcclusionPathNode" 5000       # Max: 5000
increase_pool_size "OcclusionPortalEntity" 750    # Max: 750
increase_pool_size "OcclusionPortalInfo" 750      # Max: 750
increase_pool_size "PortalInst" 225               # Max: 225
increase_pool_size "ScaleformStore" 200           # Max: 200
increase_pool_size "StaticBounds" 5000            # Max: 5000
increase_pool_size "TxdStore" 26000               # Max: 26000

The number after each line is the maximum the engine allows, so these values are already as high as they can go. If your server still crashes once they are all set, the only option left is to remove or lighten some of your content.