Contact support and report a problem

Send a support request

1. Open Support, also available from the website footer.
2. Enter your name, reply email, a specific subject, and a description in Message.
3. Click Send message and check the form's response before assuming it was submitted.

From the app, Settings... > About > Send Feedback opens an email message. If the Mac has no working email setup, use the website form instead. Keep the request in one conversation so the reproduction steps and replies stay together.

Include a useful reproduction

Write what you expected, what actually happened, and the shortest steps that reproduce the problem. This format is enough:

Subject: [Action] produces [unexpected result]
Little Tagger version and build:
macOS version:
Mac model or chip:

Steps:
1.
2.
3.

Expected result:
Actual result or exact message:
File types and approximate sizes:
Location type: local folder / external drive / cloud-synced folder / network volume
Preset or workflow action and timing, if relevant:
Checks already tried:

Find Little Tagger's version and build under Settings... > About. Apple menu > About This Mac shows the Mac and macOS information.

For a workflow, include the step order and each relevant filter. For suggestions, include the AI banner and whether the workspace contained other hidden or unselected files. For a library rename or merge, include the source and target names only when they are safe to share.

Describe purchase problems separately

Say whether the problem concerns a trial, a subscription, or a previous one-time purchase. Include the exact access message and the result of Restore Purchase.

Do not include an Apple Account password, verification code, card number, or full billing address. If a receipt is requested later, redact unrelated purchases and sensitive account details first.

Share a safe example

A small non-confidential test file is more useful than a full private folder. Before sending a screenshot, crop or cover names, paths, email addresses, and document contents that are not needed to show the problem. File tags themselves can contain private information.

Do not send a whole file collection or a copy of the app's data store unless support specifically explains why it is needed and how to share it safely.

When data may have changed

For a partial rename, merge, replacement, or deletion, keep the exact result message and describe which files changed. Avoid repeating the operation or deleting app data while preparing the report. A message such as Retry Library Sync indicates unfinished work, not an Undo function.

Suggestions and feature requests

Use the same form for a feature request. Describe the task you are trying to complete and which current step is missing. Keep feature ideas separate from a report about a failed file operation so urgent diagnostic details remain clear.