Per-file balloons vs tray flashing for multi-file queue completion in FileZilla

Question

Notification trade-off for batch transfers

FileZilla offers two primary real-time alert paths for transfer completion: system-tray balloons (one per file) and tray-icon flashing (only when minimized to tray). Sounds provide a third channel but lack per-event granularity beyond assigning a .wav file. The queue panel gives a silent, persistent status view.

Constraint: no batching or quiet-hours

Enabling "Show balloon notifications → Transfer finished" fires a separate balloon for every file in a queue. Disabling it suppresses those balloons entirely; there is no "notify only on first/last file" or "batch after N seconds" rule. The "Flash tray icon on transfer" setting works solely when the main window is minimized to the tray, not when merely backgrounded.

Decision point

For a workflow that regularly processes 20–50 file queues, the team needs actionable completion awareness without desktop notification fatigue. The options reduce to:

Per-file balloons (high noise, immediate visibility)
Tray flashing only (low noise, requires minimized-to-tray state)
Sound per event (audible cue, no visual stacking, .wav format required)
Queue panel only (zero noise, manual polling)

Which combination of balloon, flash, and sound settings gives a maintainable signal-to-noise ratio for multi-file queues on Windows 10/11, and does the tray-flash path remain reliable when the window is restored but not focused?

Tasadduq Burney · Answer

Direct answerFor 20–50 file queues on Windows 10/11, the maintainable combination is: disable per-file balloons, enable a short .wav sound (≈200 ms), keep tray flashing on, and rely on the queue panel for detail. This yields one audible cue per file without desktop clutter. Tray flashing stops working as soon as the window is restored, even if it lacks focus; it only fires while the main window is minimized to the system tray.Why this combination worksBalloons fire one per file with no batching, quiet-hours, or first/last-only option. On 50-file queues they trigger Windows notification throttling, causing later balloons to be dropped silently.Tray flash is binary: it flashes only when the window is minimized to the tray. If the window is restored (even unfocused), minimized to the taskbar, or merely backgrounded, no flash occurs.Sound plays a .wav per completed file. A short, distinct clip (click, pop) avoids overlap cacophony; long clips queue sequentially and delay awareness of later completions.Queue panel (View → Queue) provides a silent, persistent, real-time status view that survives session restarts.Configuration steps (FileZilla 3.60+ on Windows 10/11)Edit → Settings → Interface → System tray: check Minimize to tray and Flash tray icon on transfer.Edit → Settings → Notifications: uncheck Show balloon notifications → Transfer finished.Same dialog: check Play sound, browse to a short .wav (test with a 2-file queue first).Keep the queue panel visible (View → Queue) for silent verification.Verification checklistStart a 5-file queue, minimize to tray → observe flash + sound per file.Restore the window, start another 5-file queue → verify flash stops while sounds continue.Confirm queue panel updates match each sound event.One diagnostic detail that could change the recommendationDoes the team keep FileZilla minimized to tray for the entire batch, or do they regularly restore the window mid-queue? If the window is restored at any point, tray flash becomes unreliable and sound becomes the only automatic per-file signal.

Per-file balloons vs tray flashing for multi-file queue completion in FileZilla

Notification trade-off for batch transfers

Constraint: no batching or quiet-hours

Decision point

1 answer

Direct answer

Why this combination works

Configuration steps (FileZilla 3.60+ on Windows 10/11)

Verification checklist

One diagnostic detail that could change the recommendation

Your perspective belongs here.

0 question comments