Troubleshooting

Identify where the operation stops

1. No files in the list: check collection scope and folder access.
2. Files appear but names do not change: check enabled rules, scope, matching text, and intermediate steps.
3. Run is unavailable: check calculation, zero targets, settings errors, and free limits.
4. Execution fails: open result details for the affected file and reason.

Use separate copies of a few affected files to isolate the cause while investigating.

Read the row status

Warnings may still execute. Do not judge only by the Warnings / problems display filter; read each reason. Blocked rows do not execute unchanged.

Permissions, locks, and external drives

Renaming requires write access to the containing folder. Use the permission banner or Access permissions (アクセス許可) in settings to reselect the actual folder.

1. Check external and network volumes are connected and writable.
2. Check locking and permissions in Finder’s Get Info.
3. After moving files or Macs, select the folder again.
4. Revoke permissions no longer needed in settings.

Selecting a single file may not grant enough access to its parent folder. Follow the app’s folder selection prompt.

When a rule appears to have no effect

1. Check the rule’s enabled checkbox.
2. If the matched text is in the extension, use extension-only or full-name scope.
3. Match the selected Literal / Wildcard / Regex mode to your pattern.
4. Inspect Rule steps for changes made by earlier rules.
5. Check settings errors (設定を確認), including invalid regex or unreadable list files.

Errors identify the affected rule. Begin with a simple literal replacement and add conditions gradually.

Unexpected order or number gaps

Review Numbering order and Reverse. Natural, strict, and insertion order differ. Unchecking a row preserves the original preview position and can leave gaps. Limit collection or remove unwanted rows from the list to close them.

Enable restart per folder to begin at 001 in each folder. Disable it for one continuous sequence. To pad an existing number without assigning a new value, use Pad existing numbers.

Unexpected dates, camera fields, or readings

Missing EXIF, date fallbacks, unavailable metadata, and estimated kanji readings can all explain differences. Check details for an actual capture timestamp and select another date source if appropriate.

See empty or unknown tokens and correcting romanized readings.

CSV or TSV does not load or rename

1. Choose the list again if it moved.
2. Export .xlsx as CSV or tab-separated text.
3. Match the delimiter: the default is tab; enter a comma for CSV.
4. Check encoding and header settings.
5. Match old names exactly and ensure new names are not empty.
6. Use full-name scope if new values contain extensions; otherwise use base-name scope.

In line-order mode, nonempty lines correspond to preview order. Simplify complex quoted CSV or names containing delimiters/newlines; a simple tab-separated mapping is preferable.

Undo fails or only partly succeeds

Check whether files moved, were deleted, or were renamed afterward, whether original paths are now occupied, and whether access remains valid. Review the unsuccessful entries instead of repeatedly reverting successful ones.

Free history retains only the latest 10 runs. If a record is gone, it cannot be used for undo. Encoding, dates, and attributes are outside rename undo.

Only some files execute, or Pro is not active

Excluded, unchanged, and blocked rows do not count as renamed files. The free plan allows 200 per month and 30 per run, with partial execution confirmed in advance. Interdependent swaps may reduce the executable subset further.

For purchased Pro, check the purchasing Apple Account and Restore purchases (購入を復元). TestFlight and production purchases differ. For automation, also inspect processing status and the selected preset.

What to include in a report

1. Your macOS and smartRenamer versions.
2. Buttons pressed and steps leading to the problem.
3. Rules, collection scope, and whether preview, execution, or undo was affected.
4. Expected and actual names; replace private names with fictional examples of the same structure.
5. The exact error message.

Do not send confidential paths, personal information, or passwords. File attachments are not required.

Contact options ↗