Gridly is the #1 spreadsheet for multi-language content. Bring your digital assets together and localize at speed!
Manage your game’s data as a single source of truth and roll out continuous updates with full localization support & version control.
- Unreal Engine 5.4
Before you use Gridly, you will need to sign up for an account at https://www.gridly.com
Download the Gridly plugin itself, as well as the sample project to get you started:
The sample project is optional, but provides a working example project for reference that has a very basic user interface set up for localization in UE5.4.
Gridly plugin for UE5.4 leverages Unreal's built-in tools for localization. If you are not familiar with Unreal's localization pipeline, please consult their documentation.
This guide assumes that you are already familiar with Unreal's tools, and that you've correctly set up all the text in your project for localization using this workflow. The plugin supports both inline source strings and the use of StringTables.
The plugin can be installed as either an engine plugin or a project plugin.
- Extract the contents of Gridly UE5.4 Plugin repository to
Plugins/Gridly(relative to project root). - Generate project files for the project and build the project to compile the required DLLs for the project plugin.
- Extract the contents of Gridly UE5.4 Plugin repository to
Engine/Plugins/Gridly(relative to engine root). - Generate project files for the engine and build again to compile the required DLLs for the plugin.
To enable the plugin in your project, go to Edit -> Plugins and search for Gridly.
Once enabled, restart Unreal to load the plugin.
In the Localization Dashboard, you should now be able to choose Gridly as your Localization Service Provider. Once selected, close the Localization Dashboard and re-open it to load the toolbar buttons.
If you do not have access to the Localization Dashboard, you need to enable it. Go to Edit -> Editor Preferences and search for Localization Dashboard to activate it.
Once enabled, restart Unreal to be able to find the Localization Dashboard option under Window -> Localization Dashboard.
Before you can export your source strings to Gridly, you need to first set up a new Grid in Gridly. Here is an example using FIGS:
You will also need to set up your project to target the same cultures in the Localization Dashboard.
Important! Make sure these locale/culture codes match the ones on Gridly (hover over them to show tooltip). For the sample project, make sure you rename the columns on Gridly src_enUS, tg_frFR, tg_itIT, tg_deDE and tg_esES. To do this in Gridly, choose "Column Properties" on the column header. If you have previously set this up with codes that do not match those in Gridly, or you wish to map them in a different way, see how you can customize the mapping.
To communicate with the API, you need to make sure that you have configured the plugin to use the correct API keys. You also need to set which view IDs you wish to use for import/export. See import/export settings for more information.
Once you have made sure that your source and target languages are set up correctly and matching in both Unreal and on Gridly, and you have gathered all your source text, you can now export all source strings by pressing the Export to Gridly-button on the Localization Dashboard.
After export, open the Grid in your browser to edit the translations in the browser (may require refresh to see changes).
You can use the Sync records setting in the plugin settings to delete the records from Gridly that has been removed from UE. This setting may slow down the export process, because after it send to entries into Gridly, it checks whether the Grid has any record that not exists in the game target you sent.
After you're done translating, you can import translations for all target cultures back to project with just a single click.
If you have existing translations in UE5.4, these can also be exported to Gridly with a single click (you usually only need to do this once).
The Gridly plugin also supports updating translations during runtime using the provided Blueprint functions to enable preview mode:
After making changes on Gridly, the translations can then be updated using the following:
While possible, it is currently not recommended to use this mode in a production build! This functionality is for development only (either in PIE mode or Development build). When final translations are ready, you should import your translations through the Localization Dashboard.
The Gridly Data Table is a data table that can be used like a regular data table in UE5.4 as part of your game's logic. The extra functionality that this plugin provides is that the data can also be edited through the Gridly web app, and synchronized with UE5.4 both during development and even in the packaged project. To get started, right click in the asset browser to create a Gridly Data Table:
You need to select a Structure data type for each row (or a USTRUCT that inherits FTableRowBase if you're using C++). The difference between GridlyDataTable and a regular data table is that it is mapped to a particular view on Gridly. You can set the view ID that the table is mapped to in the Data Table Details panel:
For the plugin to map the data correctly between Gridly and UE5.4, the variable names of the Structure needs to be named the exact same as the column IDs of the view you are synchronizing with. Create an empty grid on Gridly and create columns with column IDs that match your Structure variables.
Currently, the Gridly Data Table supports synchronizing Boolean, Integer, Float, String and Enum types.
You can now import/export data from UE5.4 to Gridly:
All the settings for Gridly can be found in Edit -> Project Settings -> Plugins -> Gridly. They can also be found in Config/DefaultGame.ini if you prefer to edit these options by hand.
-
Import Api Key: This is the API key used for importing translations from Gridly.
-
Import from View Ids: This is a list of view IDs on Gridly to import from. We will fetch from all view IDs and combine the results. Only one record will be used in case of duplicate record IDs. This will be used for both regular import as well as in Live Preview mode.
-
Export Api Key: This is the API key used for exporting source strings. Make sure it has write-permissions.
-
Export View Id: This is the view ID on Gridly that source strings should be exported to.
-
Use Combined Namespace Id: If you have specified a namespace for your source strings, it will be combined with the key before being sent to Gridly, in the form of
Namespace,Key. Likewise, it will expect the record ID fetched from Gridly to be in this form and convert it during import. Do not change once configured! -
Also Export Namespace Column: If you are using the above option, you can optionally also export the namespace to a separate column in addition to being used in the ID for translation reference/path tag organization.
-
Namespace Column Id: The column ID on Gridly to map the namespace in Unreal to. By default, this is
path, which is the path tag column. This can be set to any column ID that is configured to be a string. This option works for both import and export. Do not change once configured! -
Source Language Column Id Prefix: All source language columns on Gridly are expected to use culture mapping as configured below and prefixed with this value. Make sure this matches the column IDs on Gridly.
-
Target Language Column Id Prefix: All target language columns on Gridly are expected to use culture mapping as configured below and prefixed with this value. Make sure this matches the column IDs on Gridly.
By default, the Gridly plugin will automatically convert language/culture codes of the format en-US in Unreal to what Gridly uses, which is generally enUS (without the hyphen). You can also completely customize this behaviour by using custom culture mapping.
