Everything RPFView does

Browse and search

• Browse the game folder like Windows Explorer, including archives nested inside archives (e.g. x64e.rpf\levels\gta5\vehicles.rpf\…).
• Reads encrypted (NG, AES) and unencrypted (OPEN) archives.
• Instant search across all ~400,000 game files.

  • Queries can be a substring, a wildcard (adder*), a path filter (path:vehicles.rpf) or an extension filter (ext:ytd,ydr). Filters combine.

Edit safely

• Edit archives:

  • Import files or folders, including drag and drop from Explorer.
  • Replace, rename, delete, create folders, create new archives.
  • Edits stay pending until you save (Ctrl+S).
• Edit mode guards against accidental changes. When you edit an archive inside the game folder, RPFView offers to copy it to the mods\ folder first, so the original game files stay untouched.
• Crash-safe saving:

  • The archive is rebuilt into a temporary file and swapped in atomically, so the original survives any failure.
  • An optional .bak backup is kept.
  • RPFView refuses to overwrite a file that another program changed meanwhile, and offers to reload it.

Export and compatibility

• Export files exactly as stored, or converted. Drag files out to Explorer, or export whole folders recursively.
• Saved archives use the same OPEN format as OpenIV. As with OpenIV, the game needs an RPF/mods loader (e.g. OpenIV.asi) to load modified archives.

View and export

• Opens .ytd texture dictionaries and textures embedded in models.
• Formats: DXT1/3/5, BC4/BC5 (ATI1/ATI2), BC7 and uncompressed.
• Preview with zoom and pan, mip levels, R/G/B/A channel toggles and a checkerboard background.
• Export as DDS (all mips) or PNG.

Edit texture dictionaries

• Texture dictionary editing:

  • Replace, add (also by drag and drop), remove and rename textures.
  • Choose the format (Auto, DXT1, DXT5, ATI2, BC7, A8R8G8B8) and mipmap generation.
  • Save back into the archive or as a separate file.
  • Mipmaps are filtered correctly per texture type: colour in linear light, normal maps as vectors, data maps on raw values.

3D viewer

• 3D viewer with orbit, pan and zoom.
• Choose LOD and drawable; textured, solid and wireframe modes; toggle individual meshes.
• Textures are found automatically:

  • embedded dictionaries,
  • .ytd files next to the model,
  • shared vehicle dictionaries.
• Vehicles are shown complete, including wheels and parts attached to bones.

Export

• Export as OBJ (+ MTL + PNG textures) or binary glTF (`.glb`).

Ped components

• Ped components:

  • Open a ped folder such as mp_m_freemode_01 and every slot is listed (head, hair, upper body, pants, shoes, hands, tops, accessories, …).
  • Step through each slot's drawables and texture variations with the arrow keys.
  • Combine slots into a complete outfit, or load the default outfit.
  • Prop folders such as mp_m_freemode_01_p open the same way: hats, glasses, earrings, watches and bracelets.
• All clothing: every component and prop of a ped from the base game and all DLC packs in one list, without picking a folder.

  • Numbered like the game, so the numbers match the ones scripts and FiveM use (top 55 is the police shirt).
  • Patch packs replace the models they fix, as in the game.
• FiveM clothing resources: in a stream folder, each collection named before the ^ is its own folder, so male, female and prop files don't mix.
• Images of every item in every texture variation come from the Thumbnail Generator.

Textures

• Texture sources: pick from the variation gallery, use any texture from the folder, or load your own PNG/JPG/DDS, also by dragging it onto the model. Phone photos are turned upright automatically (EXIF).
• Save into the texture dictionary: encodes your image and writes it into the component's .ytd.

  • Replace a specific variation or the default texture, or create a new variation with the next free letter.
  • Only diffuse (colour) textures can be changed.
• Respects the mods\ folder: if a modded copy exists, the studio works on that copy.

Weapons and attachments

• Every weapon of the base game and all DLC packs, with its tints, components, camos and finishes, read from the game's weapon files.

  • Magazines, scopes, suppressors, flashlights and grips sit on the weapon where the game puts them.
  • Tints use the weapon's own palette, so MK II weapons show all 32 of theirs.
• Pick a component for each slot (magazine, flashlight, scope, muzzle, grip, barrel, camo) and the preview redraws; Reset goes back to the weapon as it comes.
• Search by weapon, model, component or DLC pack name.
• Side view (muzzle right or left), three-quarter or top; knives and bats can be laid flat like the guns. Checker, dark, grey or white background.

Images

• Save image… saves the weapon as shown, at 1024 pixels, as PNG, WebP or JPG. PNG and WebP keep the transparent background.
• Images of every weapon, tint, component, camo and finish in one run come from the Thumbnail Generator.

Clothing

• Thumbnails → Clothing…: one image per drawable and texture variation of the slots you tick, each framed on its own.

  • All clothing of a ped: the base game and every DLC pack, numbered like the game (the numbers scripts and FiveM use).
  • Or a Folder: a ped folder such as mp_m_freemode_01, or a FiveM resource's stream folder, one collection at a time.
• Rockstar's placeholders (checkerboard textures, flat stand-in models) are left out.
• Front, three-quarter, side or back view.

Weapons

• Thumbnails → Weapons…: every weapon of the base game and all DLC packs, or one weapon, with its tints, components (on the weapon or on its own), camos and finishes.
• A livery colour for camos that can be recoloured; camos with their own colours keep them.
• Side view (muzzle right or left), three-quarter or top; knives and bats can be laid flat like the guns.

Preview and files

• Preview: every image the choices make, under its slot or weapon and with its file name, drawn as it will be saved. Images the run leaves out are faded.
• PNG, WebP or JPG from 128 to 1024 pixels, with a quality setting; PNG and WebP keep the transparent background, JPG goes on white.
• File names from a pattern such as {slot}/{drawable}_{texture} or {weapon}, with presets for FiveM: FiveM: game numbers writes the names of fivem-greenscreener, FiveM: collections the names of the collection natives.
• A run can be stopped; Skip images that already exist continues where it stopped.

• Plain .meta / .xml files are shown as they are, with XML highlighting and folding.
• Binary RSC meta (.ymap, .ytyp, .ymt), PSO (.ymt, .ymf) and RBF files are converted to readable, Rockstar-style XML.
• Hashes are resolved to names through a dictionary that RPFView builds automatically from your own game files.

• Installed next to the app. It uses the game folder and keys already set up in the app.
• rpfview-cli extract-weapon-metas: extracts all weapon metadata of the base game, the update and every DLC pack in under a second:

  • weapons.meta, per-weapon DLC files, components, animations, archetypes, vehicle weapons, loadouts, pickups;
  • about 450 files, keeping the game's folder structure.
• rpfview-cli extract "<pattern>" --out <folder> and rpfview-cli find "<pattern>" find and extract any files by name.
• Read-only towards the game; it never writes into the game folder. Good for scripts and AI agents.

• Detects the game automatically:

  • Steam libraries,
  • Rockstar Games Launcher,
  • Epic Games (launcher manifests),
  • common install folders on every drive.
• Game archives are encrypted. RPFView ships no Rockstar keys. It derives them once from the user's own GTA5.exe.

  • The second key part comes from CodeWalker's public magic.dat. RPFView downloads it from CodeWalker's GitHub only after the user ticks a consent box, or the user can pick a local copy.
  • Keys are verified against the game and cached locally, so later starts need nothing.
• If setup fails, the dialog names the failed step, says what to do, and can copy a diagnostic report (which never contains keys).

• Per-user installer: no administrator rights needed.

  • Installs to %LocalAppData%\RPFView.
  • Adds Start menu and desktop shortcuts.
• Always up to date: at startup a small window checks for a new version, downloads it with a progress bar, installs it and restarts.

  • Updates are usually small delta packages (often under 1 MB).
  • Users without a connection start normally after a few seconds.
  • Updates are mandatory, so security fixes reach everyone.
• A portable zip is also available (no install; it updates itself inside its folder).
• Small download (about 18 MB): the installer adds the .NET 10 Desktop Runtime only if it is missing.