Get help and send feedback

Report a bug or suggest an idea from Filarr, find your version number, reach the team on the website, and know what to share and what never to send.

On this page
Documentation sections

Something does not work, or you have an idea? Start with Troubleshooting and the Frequently asked questions: the answer may already be there. Otherwise, write to us from Filarr itself, or through the website.

Send feedback from Filarr

  1. Open Settings → Feedback. You can also type "feedback" in the search box of the Settings.
  2. Click Send feedback.
  3. Choose the Feedback type: Bug, Feature or Other.
  4. Describe the problem or the idea in Description.
  5. If you want an answer, enter your address in Email (optional). Without it, we cannot reply.
  6. Click Send.

Under the email field, the System info attached automatically box shows exactly what Filarr adds to your message: the Filarr version, the type of system and its language. Nothing else is attached: no file, no note, no list of your data.

When the message is sent, Filarr says Thank you! Your feedback has been sent.

Without a network

You can write feedback offline. Filarr then says Thank you! You are offline right now and keeps the message on your device. It sends it by itself the next time a message goes through, or the next time Filarr starts with a connection. Filarr keeps up to the 20 most recent messages waiting.

Find your version number

Open Settings → About. The Version row shows the number, for example v3.5.9. The feedback window shows it too, in the system info box.

In the desktop app, the same page has Check for updates. Before you report a bug, check that you have the latest version: the problem may already be fixed.

Contact the team on the website

In Filarr, Help in the sidebar, right under Settings, opens this help. It is also online, at https://filarr.com/en/docs.

The Support the project row in Settings → About, and the page https://filarr.com/en/support, are for donations to the project. They are not a help desk.

What to put in a bug report

A good report lets us reproduce the problem. Include:

  • What you were doing, step by step, from the start.
  • What you expected, and what happened instead.
  • The exact message Filarr showed, copied word for word or in a screenshot.
  • Where it happens: the desktop app on Windows or on Linux (with the name of your distribution), or the web app with the name of your browser.
  • Your Filarr version.
  • How often it happens: every time, sometimes, once.
  • The kind of profile: local profile or cloud account.

Before you attach a screenshot, check that it shows none of your files, notes or personal details.

What never to send

A share link carries the key of the file inside its address: anyone who has the full link can open the file. If you need to tell us about a link, describe it instead of pasting it.