FName in Unreal Engine
source: https://dev.epicgames.com/documentation/en-us/unreal-engine/fname-in-unreal-engine?application_version=5.8 version: Unreal Engine 5.8 Documentation fetched: 2026-10-11（curl 抓取页面文本，去掉 HTML；原文全文，供 wiki 页面引用）
FName in Unreal Engine | Unreal Engine 5.8 Documentation | Epic Developer Community Table of Contents Developer FName FName Reference for creating, converting, and comparing FNames in Unreal Engine. On this page FNames are a lightweight type used for efficient string handling. Specifically, Unreal Engine maintains a global table of unique strings, and an FName stores an instance number and an index reference to a given string, facilitating quick lookup and access. Additionally, the FName subsystem uses a hash table to provide fast string-to-FName conversions. FNames are particularly useful for representing object names, identifiers, and other strings that are frequently compared. When you name a new asset in the Content Browser , change a parameter in a Dynamic Material Instance, or access a bone in a Skeletal Mesh, you are using FNames . FNames are case-insensitive, immutable, and cannot be manipulated. Creating FNames FName TestHUDName = FName(TEXT("ThisIsMyTestFName")); Copy full snippet FName TestHUDName = FName(TEXT("ThisIsMyTestFName")); Conversions FNames can only be converted to FStrings and FText, and can only be converted from FStrings. From FName From To Example FName FString TestHUDString = TestHUDName.ToString(); FName FText TestHUDText = FText::FromName(TestHUDName); FName -> FText is valid in some cases, but be aware that the FNames's content will not benefit from the FText's "auto localization". To FName From To Example FString FName TestHUDName = FName(*TestHUDString); FString -> FName is dangerous as the conversion is lossy as FName's are case insensitive. FText FName There is no direct conversion from FText to FName. Instead, convert to FString and then to FName. FText -> FString -> FName is dangerous as the conversion is lossy as FName's are case insensitive. When doing these conversions, be aware that they may contain characters that are not valid for the type of FName you are creating. The INVALID_NAME_CHARACTERS macro in NameTypes.h defines which characters are invalid for FNames, and several functions within FName (such as IsValidObjectName() ) check the validity of FNames for particular use cases. Comparisons The == operator can be used to compare two FNames, and returns true or false. Rather than doing string comparisons, this compares the values in Index, which is a significant CPU savings. FName::Compare can also be used to compare two FNames, and it will return less than 0 if this less than Other, 0 if this equal to Other, and greater than 0 if this greater than Other. CompareFloat = TestFName.Compare(OtherFName); Copy full snippet CompareFloat = TestFName.Compare(OtherFName); Using FNames Using an FName is pretty straightforward. Let us say that you wanted to get the bone named pelvis from the Skeletal Mesh Component of an Actor. The C++ code below shows the use of an FName constructed on the fly while being passed to GetBoneRotation() . FRotator rotPelvis = Mesh->MeshGetInstance(this))->GetBoneRotation(FName(TEXT("pelvis"))); Copy full snippet FRotator rotPelvis = Mesh->MeshGetInstance(this))->GetBoneRotation(FName(TEXT("pelvis"))); This creates an FName that is passed to GetBoneRotation() , which returns the FRotator for that corresponding bone. The name of the bone gets loaded into the FName table when the package loads, so the constructor for the FName finds the bone's name in the hash table, avoiding an allocation. Searching the Name Table If you want to determine if an FName is in the name table, but you do not want to automatically add it, you can supply a different search type to the FName constructor: if( FName(TEXT("pelvis"), FNAME_Find) != NAME_None ) { // Do something } Copy full snippet if( FName(TEXT("pelvis"), FNAME_Find) != NAME_None ) { // Do something } If the name does not exist in the name table, the Index of the FName is set to NAME_None . Note that we are not checking a pointer for null as you would with a normal string. programming strings fname ftext fstring Ask questions and help your peers Developer Forums Write your own tutorials or read those from others Learning Library On this page Creating FNames Conversions From FName To FName Comparisons Using FNames Searching the Name Table