Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Attribute Changer?
Attribute Changer is a free Windows utility for changing file and folder metadata that Explorer normally makes awkward to edit: timestamps, filesystem attributes and filename casing. It is made by a Luxembourg/European developer, and the official page presents it as free for personal and commercial use.
Its core jobs are straightforward: set absolute date and time stamps, add or subtract time values, randomize dates, uppercase/lowercase/capitalize names, and toggle attributes such as Read-Only (to stop applications saving over a file) or Hidden. For photos, it can modify or add EXIF date and time information in JPEG files.
The more advanced features are aimed at people managing many files at once. Batch processing can be narrowed with filters on attributes, date and time, file size and name (including wildcards like *.TMP), and there is a simulation mode so you can preview what a change would do before applying it. Changes are logged in real time, with old and new values shown side by side, and logs can be exported as CSV for spreadsheets or archiving.
Who it suits
- Photographers and archivists fixing missing or wrong capture dates across photo collections.
- System administrators and power users bulk-adjusting timestamps or attributes for backups, sync tools or cleanup scripts.
- Anyone tidying large folders who wants consistent naming or folder dates derived from the newest or oldest file inside.
Trade-offs to weigh
It is a focused metadata tool, not a file manager or backup program, and it is Windows-only. Batch changes to timestamps can affect how sync and backup software decides what to copy, so the simulation and logging features are worth using before committing. The developer explicitly warns against downloading from third-party portals that bundle nagware, so get it from the official site: Attribute Changer.
As a next step, if you are preparing a photo archive, start with a small test folder: filter to JPEGs, use simulation to check the proposed EXIF dates, then apply and export the log as a record of what changed.
How do I change the date and time of a photo using Attribute Changer?
Attribute Changer changes a photo's date and time by editing the image's EXIF metadata, not by altering the picture itself. In the tool's options you can set an absolute date and time, add or subtract an offset, randomise values, or synchronise dates across files, and it also supports partial edits such as changing only the day or only the minute. Because the same engine handles batch processing, you can apply one correction to a whole folder of photos rather than editing each file by hand.
A practical workflow
- Select the photos you want to correct.
- Choose whether to set an exact timestamp or shift the existing one (for example, add two hours to compensate for a camera set to the wrong time zone).
- Use the filter options to tag only the files you mean to touch—by date, size, name or attributes—so unrelated images are skipped.
- Run a simulation first if you want to preview the result without committing changes.
- Check the realtime log, which lists old and new values side by side, and export it to a CSV if you need a record.
When this approach fits
This is most useful for photographers and archivists fixing camera clock errors, filling in missing photo dates, or reordering files by capture time. The main trade-off is that EXIF edits change metadata, not the file's creation date on disk, so tools that read the filesystem timestamp rather than EXIF may still show the old value. Keep a backup of originals before batch edits, since bulk offset changes are easy to apply to the wrong selection.
For background on how photo metadata is structured, ExifTool documents the EXIF date fields Attribute Changer writes to, and Attribute Changer is the official source for the software.
Can Attribute Changer batch process files using filters like name, size, or date?
Yes. Attribute Changer is built around batch processing, and its filters are the mechanism that decides which files and folders get changed. According to the product page, you can filter on attributes, date and time, file size, and name. Name filters accept wildcards such as *.TMP or WRD?????.DOC, and the page notes special -T, -D, and -F directives for tagging specific object types.
Where filters fit in a real workflow
A practical case is cleaning up a folder of scanned documents before archiving: filter by name pattern (say, SCAN*.PDF) and by a date range, then apply new timestamps or set the Read-Only attribute in one pass. The page also lists simulation and detailed logging with before/after values, plus CSV export, so you can preview a filtered batch and keep a record of what changed.
Decision criteria
- Precision matters more than speed: combine name and date filters so a broad wildcard doesn't catch files you meant to leave alone.
- You need an audit trail: the side-by-side old/new value log and export suit compliance or tidy-up work.
- You only need one-off edits: a file manager's built-in properties dialog may be simpler than setting up a batch.
For broader file-management needs, see Attribute Changer and, for general Windows file handling, Microsoft. A sensible next step is to run a simulated batch on a small test folder before applying filters to a large archive.
How do I make a file read-only or hide it with Attribute Changer?
Set the Read-Only or Hidden attribute on the file through Attribute Changer's attribute options, then apply the change. Attribute Changer is a Windows shell extension: after installation it adds its own entry to the right-click context menu of files and folders, which is where you open it. The page describes these as filesystem attributes you can change, so the operation is the standard Windows Read-Only and Hidden flags rather than encryption or password protection.
Read-Only
- What it does: Marks the file so applications treat it as protected from saving changes. The page's stated purpose is to prevent applications from saving changes to a file.
- Practical limit: It is a courtesy flag, not a lock. Many programs warn and then save anyway, and any user who can edit the file can clear the attribute. Use it to stop accidental overwrites of templates, reference documents or archived originals, not to secure sensitive data.
Hidden
- What it does: Sets the Hidden attribute so the object is hidden from normal views.
- Practical limit: Hidden items reappear as soon as Explorer's "Hidden items" view is switched on. It reduces clutter; it does not conceal anything from someone who looks.
Doing it to many files at once
This is where the tool earns its place. In the same dialog you can select a whole folder tree and use the filter options to tag only the objects you want: filter by attributes, date and time, file size or name, with wildcards such as *.TMP or WRD?????.DOC. That lets you, for example, mark every .bak file in a project folder as Read-Only in one pass instead of right-clicking each one.
Two features make bulk changes safer:
- Simulation lets you preview what would change before committing.
- Logging and export record old and new values side by side, and the log can be exported as a comma-separated file for a spreadsheet or an archive. That is a genuine audit trail if you are changing attributes across a shared drive.
A concrete scenario
A designer keeps a folder of master logo files that colleagues copy into layouts. She opens the folder in Attribute Changer, filters to the master file types, sets Read-Only on them, runs a simulation to confirm the list, then applies it. When someone tries to save over a master, the application warns them. The log export gives her a dated record of exactly which files were protected and when.
Decision criteria
- A handful of files, one-off: the standard Windows Properties dialog is faster; Attribute Changer adds little.
- Many files, filtered selection, or a need for a record: Attribute Changer's batch filters, simulation and log export are the reason to use it.
- Actual confidentiality: neither attribute qualifies. Use NTFS permissions or encryption instead.
As a next step, run one batch with simulation enabled first and check the log before applying, so you can see exactly which objects your filter caught. The tool is offered free of charge for personal and commercial use from its official site, Attribute Changer, and the author specifically warns against download portals that bundle unwanted software.
Is Attribute Changer safe to download, and where should I get it?
Yes—provided you download it from the developer's own site at Attribute Changer. The page states the software is free of charge and is not bundled with nagware or malware.
Why the source matters here
The developer explicitly warns against getting the tool from CNET/Download.com and other download portals, which the page says push nagware and malware, and notes that some sources try to charge for a download that is free. That makes the official site the only source the developer endorses. The page also says the software is free for personal and commercial use.
A practical rule for any small Windows utility like this: if a site asks you to pay for it, bundles an "installer helper," or wraps the download in extra offers, stop and go to the developer's page instead. For Attribute Changer specifically, the official site is where you should start.
A quick safety routine
- Download only from the developer's site linked above, not from aggregator portals or search-ad results.
- Check the version and release date shown on the page against what you receive; the page lists version 11.50a, released 24 September 2026.
- Scan the installer with your usual antivirus before running it, as you would with any download.
- Before a bulk operation—changing timestamps or attributes across many files—use the simulation option the page describes, and keep the exported change log so you can review what was altered.
When this fits
Attribute Changer suits people who need to adjust file dates, EXIF photo timestamps, attributes, or filename casing in batches on Windows, and who value the logging and simulation features. If you only occasionally rename a file or check a date, the built-in Windows tools may be enough and there is no reason to install anything.
How can I log and export the changes Attribute Changer makes to my files?
Attribute Changer records every modification it performs and lets you export that record as a comma-separated text file. The page describes two parts of this: a real-time change log, and a Reporting tab where failed actions appear. You can switch on a more detailed view at any time to see a complete list of all activity, with old and new values shown side by side for comparison. The Export log option writes the logged activity to a CSV file you can open in a spreadsheet or archive.
A practical workflow
- Before running a batch job, decide whether you need the full detail view or only failures. The full view is more useful when you are verifying results; the default is lighter when you only care about errors.
- Run the operation, then check the Reporting tab for failed actions before exporting.
- Export to CSV and open it in a spreadsheet. The side-by-side old and new values make it easy to sort by file name and confirm each change.
- Keep the CSV with the job's notes if you are redating folders or randomising timestamps, since those changes are hard to reconstruct later.
What the log is good for
- Auditing a bulk rename or case change. If you uppercase, lowercase or capitalise names across many files, the log is your only record of the original names.
- Checking photo metadata edits. When you modify or add EXIF date and time in JPEGs, the old and new values let you confirm nothing was overwritten incorrectly.
- Debugging filters. If a batch touched files you did not intend, the log shows exactly which objects matched your attribute, date, size or wildcard name filters.
- Recovering from mistakes. Read-only and hidden attribute changes are easy to reverse, but only if you know which files were affected.
Limits to plan around
The log records what Attribute Changer changed; it is not a backup. Exporting after a job gives you a record, not the original file contents, so keep separate copies of anything irreplaceable before large batch operations. Also export promptly: the page does not describe the log as persistent across sessions, so treat the CSV as the durable artefact.
As a next step, run a small test batch on a copy of a few files with the detailed view enabled, export the CSV, and check that the columns give you the old and new values you need before scaling up to the full folder. For a second opinion on file-attribute tools generally, Attribute Changer is the official source for this program.
User reviews (0)