FileZilla 3.x Sound Alerts: Moving to a Failure-Only Setup

Question

The goal is an alert setup where a sound always means a transfer failed, while successes stay silent because the queue panel already shows their status. FileZilla Client documents a Sounds page in its settings dialog (Edit > Settings > Sounds in common builds) with toggles for events such as successful transfers, failed transfers, and connection events, which appears to support this failure-only arrangement.

Two constraints complicate the decision. Sound events, their labels, and default states have shifted across the 3.x line, so older writeups may not match a current install; the page should be checked against the version in use. The client also offers no native conditional alerting — no built-in filter by server, transfer size, or repeated failures — so finer-grained alerting would require external log parsing or scripting.

A product boundary matters too: FileZilla Server's logging is configured separately from the client's sound settings, and server 1.x replaced the 0.9.x administration interface, so guidance does not transfer between the two products.

Can success and failure transfer sounds be toggled independently in current 3.x builds, or do they share a single event?
When a multi-file queue partially fails, does the failure alert fire once per failed file or once for the whole queue?
Is there any documented hook for conditional alerting, or is external log parsing the only route?

Tasadduq Burney · Answer

Answer
Yes – the successful‑transfer and failed‑transfer sounds can be turned on or off independently. When a queue contains multiple files and some of them fail, the failure sound plays for each individual failed file. FileZilla does not provide any built‑in hook for conditional alerting (per‑server, size‑based, repeat‑failure, etc.); achieving such filtering requires external log monitoring or a wrapper script.
Confirmed facts (based on current 3.x builds)

The Sounds page (Edit → Settings → Sounds) shows separate check‑boxes labelled “Successful transfer” and “Failed transfer”.
  Disabling the successful‑transfer box and enabling the failed‑transfer box results in silence on successful transfers and an audible alert for each failed transfer.
  No native conditional sound‑alert API is exposed in the client; the client log (viewable via Edit → Settings → Logging) records each transfer outcome and can be parsed externally.

Likely explanation for version‑specific label differences
Across the 3.x series the exact wording of the sound‑event labels has been tweaked (e.g., “Transfer succeeded” vs. “Successful transfer”). Older documentation may therefore not match the current UI, but the underlying functionality – independent toggles and per‑file failure alerts – has remained consistent.
Steps to configure a failure‑only setup

Open FileZilla Client.
  Navigate to Edit → Settings → Sounds.
  Uncheck the box for “Successful transfer” (or similarly named success event).
  Check the box for “Failed transfer” (or similarly named failure event).
  Optionally adjust the volume slider to a suitable level.
  Click OK to save.
  Test: enqueue a file that will succeed and another that will fail (e.g., by pointing to a non‑existent remote path). You should hear no sound for the success and a sound for the failure.

Missing diagnostic detail
To ensure the label names match your build, please confirm the exact version of FileZilla you are running (e.g., 3.60.2). If you are using a very early 3.x release (< 3.50), the checkbox wording may differ and you would need to locate the equivalent success/failure entries.

FileZilla 3.x Sound Alerts: Moving to a Failure-Only Setup

1 answer

Answer

Confirmed facts (based on current 3.x builds)

Likely explanation for version‑specific label differences

Steps to configure a failure‑only setup

Missing diagnostic detail

Your perspective belongs here.

0 question comments