Batch Rename and File Tagging in elementary OS

Files, the Pantheon file manager bundled with elementary OS, handles much of the daily work involved in moving, opening and sharing documents. Its batch rename tool gives that work a predictable pattern, while file tags add context without changing what a file is called. Together, they can keep a chaotic Downloads folder understandable and make a large reference library easier to search.

The distinction matters because a filename identifies a file, whereas a tag describes its purpose or status. A Brisbane photographer might rename image exports from a weekend shoot, then mark the keepers as selected. A Melbourne office can label year-end documents as archived while leaving their names intact for accounting software. Files supports both approaches, although the exact labels and available options can differ slightly between elementary OS releases.

Understand what each change does

A rename changes the name recorded for a file in its directory. It does not alter the document, image or video inside it. During a batch rename, Files can replace matching text, apply a new prefix or suffix, change letter case, and add sequential numbers. The available controls depend on the version, and some dialogs distinguish between the base filename and the extension. That distinction is important when a folder contains both photographs and text documents.

A tag is descriptive metadata attached to a file rather than part of its name. It can represent a category, priority or workflow state, such as “Receipts”, “Selected” or “Needs review”. This makes tags useful for information that changes: a report can become “Final” without receiving another filename. Tagging support depends on the installed version of Files, and another file manager may not display the same tags even when the underlying files remain available.

Renaming and tagging therefore solve different problems. Renaming is best for establishing a consistent identifier that software, cloud storage and other people will recognise. Tagging is best for temporary classifications that should not alter that identifier. Keeping those roles separate prevents filenames from filling up with status words such as “new”, “old” or “final final”.

Prepare files before changing names

Before a large rename, make a copy of the affected folder or archive the original files. A duplicate set provides a straightforward recovery path if a pattern turns out to be wrong. This is particularly sensible when the files feed into an automated workflow, because a single altered name can break a script, shortcut, playlist or bookmark that points to the old location.

Choose the files carefully in Files. The list view, sorted by name, often makes a consecutive group easier to identify than the icon view. Depending on the selection model, Ctrl-click can add separate files and Shift-click can extend a selection. Review the highlighted count and the filenames before opening the rename panel, and avoid renaming an entire search result when only some matches need changing.

Use a naming convention that remains clear outside its original folder. Australian offices commonly read dates as day, month and year, making a filename such as 03/04 ambiguous between 3 April and 4 March. An ISO-style date such as 2025-04-03 sorts predictably and avoids confusion. For batches, decide in advance whether the extension should retain its original case and whether the numbering should begin at zero or one.

Perform a controlled batch rename

Select the intended files, right-click the selection and choose Rename. Some elementary OS releases label the action “Rename N Files”, making it easier to confirm that every selected item is included. The dialog may offer direct text fields, a search-and-replace control, or a template-style panel. These are variations of the same task, so use whichever interface is present without assuming every release contains identical controls.

Text replacement works well when filenames share a predictable fragment. For example, replacing DSC with Brisbane-shoot can turn several camera exports into recognisable names. Numbering options are useful for producing ordered sequences, with controls for a starting value, increment and leading zeros. Case settings can standardise extensions such as .JPG, but avoid unnecessary changes when a mixed-case pattern already carries meaning.

Always inspect the preview before applying the rename. Look for duplicate destinations, missing numbers, unexpected extensions and files that should not have been selected. If the destination already exists, respond to any warning rather than assuming it will be handled safely. A test run on two or three copies can confirm how the dialog handles padding, case and extension settings before an entire directory is processed.

A camera export might move from names such as DSC_0001.JPG and DSC_0002.JPG to 2025-06-14-brisbane-001.JPG. The same operation can prepare invoices from a business package, but search for references to the old names first. Desktop launchers, shell scripts, media libraries and accounting links may rely on an exact path, and renaming a file without updating those references can leave a workflow functioning incorrectly.

Match each method to the task

The fastest method depends on whether information belongs in the filename, metadata or directory hierarchy. Each option has a different strength, and using only one can make an otherwise sensible system difficult to maintain.

Batch renaming is strongest when an identifier must travel consistently through cloud storage, email and external programs. Tags are stronger when the classification is personal, temporary or likely to change. A serious archive can combine all three: folders for broad ownership, filenames for stable identity, and tags for review state or subject.

For everyday use, keep folder names broad and filename rules specific. A folder named Tax records 2025 already establishes the year, so individual files might use 2025-07-14-supplier-invoice.pdf. Adding “important” to that filename is less useful than applying a tag, because importance is subjective and may be revised. This division also makes searching more predictable.

Use tags as flexible metadata

In an elementary OS release that includes file tagging, select one or more files and open the context menu. Look for an option called “Tags”, “Add Tag” or similar wording. Existing tags can be applied directly, while some versions allow a new label to be created from the same menu. If the command is missing, check the installed version of Files and its optional plugins, since tagging is not present in every build.

A small set of meaningful labels works better than a large personal colour palette. Names such as “Keep”, “Draft”, “Receipt”, “To file” and “Shared” describe an action or purpose clearly. Where multiple tags are allowed, combine only categories that will help later searches, such as “Receipt” and “Paid”. Colour can reinforce a label, but colour alone becomes ambiguous when the same dot appears on unrelated documents.

Tags are particularly valuable for files whose names should remain stable. Photos can carry tags for the location and selection status, while contracts can carry “Signed” or “Renewal due”. In releases with a tags area in the Files sidebar, that area provides a quick route back to tagged items. Even without a dedicated filter, desktop search may find the label as searchable metadata.

Do not treat tags as the only copy of essential information. Some applications, transfer services and archive formats omit metadata they do not understand, and other Linux desktops may show the file without its labels. The rule to remember is simple: names identify, tags classify, folders group, and backups protect. Copy important material, then rename and tag it from that protected copy so every operation remains reversible.

Keep a dependable file-management routine

A dependable routine separates capture, naming and classification. Files arriving from a camera, scanner or downloaded document service enter a working folder. They are given a consistent name, checked for duplicates, tagged for their next action, and then moved into a durable location. The system need not be elaborate; repeating the same sequence is more valuable than maintaining a complicated directory tree that changes every week.

Australian small businesses can apply this pattern to documents exported from Xero, MYOB or Square Australia. A Sydney tradie might rename exports to 2025-06-14-square-invoice.pdf, while a Perth workshop could use 2025-06-14-myob-bill.pdf. Household files from MyAusPost or Australia Post can follow the same date convention, with a “Receipt” tag replacing a vague “important” marker in the filename.

Timestamps need care when files from different regions are combined. Brisbane uses Australian Eastern Standard Time throughout the year, while Sydney and Melbourne change their clock offsets for daylight saving. Adelaide sits half an hour behind Brisbane. Sorting by modification time may therefore place a file created earlier in the day after another one, so the filename or embedded capture date should remain the authoritative reference.

Experienced users can extend the routine with scripts, but the principle stays the same: every automated change should be predictable and recoverable. Keep original names in a manifest, use a small test set, and preserve a backup until the new pattern has proved reliable. The rule to remember is simple: names identify, tags classify, folders group, and backups protect.