Home / GIS and Open Map Data for Beginners

QGIS Rename Field: Alias, In-Place Rename, and Refactor Fields Compared

Close-up of hands typing on a keyboard in an office

Photo: Jakub Zerdzicki / Pexels

Sooner or later a layer arrives with fields named like license plates: fld_07, NAME_1, a column of abbreviations meaningful only to whoever exported it in 2014. You want to rename them. QGIS offers several ways, and they are not interchangeable: one changes what you see and nothing else, one changes the data where the format permits, and two write an entirely new layer with the schema you actually want. Picking the wrong one wastes an afternoon or, worse, produces a file whose names silently differ from what you set. This guide separates the routes by the only question that matters, what survives, and walks each one.

Interactive tool

Rename It for Real: The Permanence Checklist

Check off each step as you finish it. Your progress stays on this page.

0 of 7 complete

0% done

The Four Routes at a Glance

RouteWhat changesSurvives closing the project?Survives exporting the layer?
AliasThe display name inside QGIS onlyYes, if the project is savedNo, the file keeps its real names
In-place rename (Fields tab)The layer's actual schemaYesYes, where the provider allowed it
Rename Field algorithmOne field, in a new layerYes, in the new layerYes
Refactor Fields algorithmNames, types, order, and set, in a new layerYes, in the new layerYes

Read the table as the article in miniature. If the rename is for your own comfort while you work, an alias is honest and instant. If the rename must be true for everyone who ever opens the data, you need one of the other three, and which one depends on your data format and how much else about the schema needs fixing.

Route One: The Alias, a Display Name Only

An alias is a label QGIS shows instead of the field's real name. Set it in the layer's Properties, in the Fields tab or the Attributes Form settings, by typing into the Alias column. From then on the attribute table, forms, and field lists show your friendly name, while the underlying file keeps its original field untouched. Aliases are stored in the project (and can be stored in the layer's style), so they survive closing and reopening your work. What they do not survive is departure: export the layer, hand the file to a colleague, open it in another program, and the names revert to the originals, because the alias never lived in the data. This is a feature when the data is someone else's standard product whose schema other tools depend on: you get readable names without breaking the contract. It is a trap when you believe you renamed something you only relabeled.

Route Two: In-Place Rename in the Fields Tab

QGIS also lets you edit the schema directly: open the layer Properties, Fields tab, toggle editing, and rename the field in place. When it works, this is the true rename, written into the layer itself. The catch is the provider: whether in-place schema editing is allowed depends on the data format and its driver. GeoPackage and database-backed layers are generally cooperative; some formats are read-only in parts or in whole, and QGIS will refuse or grey the option rather than fake it. There is a second caution: renaming in place edits the only copy if the layer is your master data. The algorithm routes below exist precisely because writing a new layer is often the safer professional move: the original stays untouched until the new schema is proven. If you rename in place, do it on a backup or accept that the old name is gone.

Hands typing on a black laptop keyboard
Hands typing on a black laptop keyboard

Route Three: The Rename Field Algorithm

When you need one field renamed in the data itself, the Processing algorithm Rename Field is the surgical tool. Find it in the Processing Toolbox under the vector table tools, choose the layer, the field, and the new name, and run it. The output is a new layer, identical to the input except for that field's name, written wherever you tell it: a temporary layer to inspect, or a file to keep. The original layer is not modified. This route always works regardless of provider stubbornness, because it never edits in place; it reads and rewrites. Its cost is the discipline of file management: you now have two versions of the layer, and the project, your exports, and your colleagues must all end up pointing at the new one. Name output files like decisions, with the schema change visible in the file name or a README note, or the rename will confuse the next person more than fld_07 ever did.

Route Four: Refactor Fields, the Schema Workshop

When the renaming is part of a larger cleanup, wrong types, wrong order, fields to drop, lengths to fix, Refactor Fields is the workshop. The algorithm presents the layer's schema as an editable mapping: for each output field you set the name, the type, the length and precision, and the source expression it is filled from, which is usually the matching input field but can be any expression. Fields you omit are dropped; fields you reorder come out reordered. Run it and a new layer emerges with exactly the schema you specified. This is the professional route for preparing data for publication or exchange, because it fixes in one pass the whole class of problems that accumulate in received data, and because the mapping is explicit: the dialog itself is documentation of what changed. It is also the route our attribute table guide points to when a table needs more than reading and editing.

The Shapefile Trap: Ten Characters, Silently

Every route above collides with one format's hard limit. The shapefile's attribute table, a dBASE file, allows field names of at most ten characters, and it enforces the limit by truncation. Export a layer with a field named population_2024 to shapefile and the file will contain something like population or populatio, chosen by truncation, and two distinct long names that share their first ten characters will collide and be mangled into numbered variants. Nothing warns you at conversational volume; the export succeeds and the schema is quietly wrong. The defenses are simple once the limit is known: design names of ten characters or fewer when shapefile is the destination (pop_2024 survives intact), or deliver in GeoPackage, which has no such limit, and let the names be as clear as they deserve. Half the mysterious renamed fields in shared GIS data are this limit, still collecting victims decades after the format froze.

Choosing the Route: A Short Decision Path

Ask two questions. Must the new name be true outside your project? If not, stop at an alias; it is instant, reversible, and honest about what it is. If yes, ask the second: is this the only schema change the layer needs? If yes and the provider cooperates, rename in place, on a backup; if the provider refuses, or you want the original preserved, use Rename Field. If the schema needs several changes, skip the piecemeal routes and go straight to Refactor Fields, producing one clean layer in one documented pass. Whichever route you take, finish by opening the attribute table of the result and reading the column heads aloud. A rename is only real when the table in front of you, in the file your recipient will open, says what you meant it to say. For the computing side of fields, values rather than names, our field calculator guide is the companion read.

A Worked Cleanup: From License Plates to a Publishable Schema

Watch the four routes cooperate on one received layer, a habitat survey whose fields arrive as fld_01 through fld_09 plus two cryptic exports, SURV_DAT and OBS_NM. The working session goes like this. First, aliases for everything, immediately: the table becomes readable in the project's own terms (survey_date, observer, species, count) while you decide what the published schema should be, and the field season's other work proceeds on friendly names at zero risk. Second, when the dataset is frozen for publication, Refactor Fields in one pass: the real names set to the publication standard, SURV_DAT retyped from text to a true date, the two internal working fields dropped by omission from the mapping, the key fields moved to the front. Third, the deliverable check against its destination: the funder wants shapefile, so every chosen name is audited against the ten-character limit before the export, and survey_date, at eleven characters, becomes survey_dat by decision rather than by truncation's coin flip. The original file never changed at any point in that story; aliases carried the working phase, one refactor carried the publication, and the limit was met on purpose. That is the whole article in one layer's biography: display for the present, rewrite for the record, and the format's constraints consulted before they are suffered.

Renaming in Databases and Other Providers

A last provider note, because the in-place route's behavior follows the data's home. Layers served from databases (PostGIS and its kin) and GeoPackages generally accept schema edits through QGIS's provider machinery, subject to the database's own permissions and naming rules, which may be stricter than QGIS's dialog suggests: a rename your account lacks rights to perform will fail at the provider, not the interface. File formats at the read-only end of the spectrum refuse in place entirely, which is information, not malfunction. The algorithms remain the universal solvent precisely because they ask the provider only to read, then write somewhere new. When a rename matters and the provider's answer is unclear, do not negotiate: refactor to a fresh file in the format you control, verify the schema there, and make that file the layer. It is the same escape-hatch logic our geodatabase guide teaches, and it generalizes across QGIS: reading is negotiation, writing fresh is sovereignty.

Related Guides

If this page answered part of the question, these GIS guides cover the rest of the same ground:

Frequently Asked Questions

How do I rename a field in QGIS permanently?

Use the Processing algorithm Rename Field for a single field, or Refactor Fields for several changes at once. Both write a new layer with the new schema. An in-place rename in the Fields tab of layer Properties also works where the data provider allows it, but the algorithms work everywhere because they rewrite rather than edit.

What is the difference between an alias and a rename in QGIS?

An alias changes only the name QGIS displays inside your project; the underlying file keeps its original field name, and the alias disappears when the data is exported or opened elsewhere. A rename changes the schema of the data itself and travels with the file.

Why did my field names get cut off when I exported to shapefile?

Shapefile attribute tables limit field names to ten characters and truncate longer names without asking. Two names sharing their first ten characters collide and are numbered. Design names of ten characters or fewer for shapefile, or export to GeoPackage, which has no such limit.

Does Refactor Fields change my original layer?

No. Refactor Fields reads the original and writes a new layer with the schema you mapped: renamed, retyped, reordered, and dropped fields as specified. The original stays untouched, which is why it is the safe route for cleaning received data.

Can I rename a field in a shapefile directly?

The schema of a shapefile is constrained, and in-place editing is limited; the dependable route is Rename Field or Refactor Fields writing a new shapefile, keeping new names within the ten-character limit so they survive intact.

Photo credits: Jakub Zerdzicki (Pexels); Szabó Viktor (Pexels). Photos are served from this site; follow the credit to the library page for the original.