Patching Overview

Creating updated content packages which allow you to update your project after release.

Windows
MacOS
Linux

Once you have released your project, you will probably make updates to it after the initial release. This process is known as patching. Patching usually includes new content that addresses known issues, or that fixes vulnerabilities in the original release.

Different Methods for Patching

There are several methods for creating patches, but they all use one of two approaches. One approach keeps files from the original release or previous patches, but adds a pointer to new content. The other approach is to transform the content in the original build using a binary patch.

Note: You can build patches in Unreal Engine 4 (UE4) for many different platforms. However, we do not support distribution of patches for your project. Each platform has their own system for uploading patch files, and for distributing those patch files to users. For information on these platform-specific distribution systems, see the documentation for that platform's Software Development Kit (SDK).

Platform-Agnostic Patching Method

There is a method for creating patches in Unreal Engine 4 that will technically work on any platform. This method packages the entire build with new content, while the changes between the two builds are placed in a sidecar file that is added to the original file. The new PAK file is labeled with a "_p" suffix. For example, if the original build file is called `MyGamesStuff.pak`, your patch file would be called `MyGamesStuff_p.pak`.

Windows Patching

Windows uses the method described in Platform-Agnostic Patching Method .

For more information on platform-agnostic patching, see How to Create a Patch.

Help shape the future of Unreal Engine documentation! Tell us how we're doing so we can serve you better.
Take our survey
Dismiss