diff --git a/CONFIGURATION.md b/CONFIGURATION.md
index ea70227a..30ecf172 100644
--- a/CONFIGURATION.md
+++ b/CONFIGURATION.md
@@ -1,7 +1,11 @@
 # FlexASIO Configuration
 
-FlexASIO does not provide a graphical interface ([GUI][]) to adjust its
-settings. This is because developing a GUI typically requires a
+**Tip: instead of editing the FlexASIO configuration file directly, you might
+find it easier to use a third-party tool such as flipswitchingmonkey's
+[FlexASIO GUI][FlexASIO_GUI].**
+
+FlexASIO does not provide an official graphical interface ([GUI][]) to adjust
+its settings. This is because developing a GUI typically requires a
 significant amount of developer time that FlexASIO, sadly, doesn't have.
 This explains why nothing happens when you click on the ASIO driver
 "configure" or "settings" button in your application.
@@ -383,6 +387,7 @@ automatic conversion mechanism as the one this option controls.)
 [issue87]: https://github.com/dechamps/FlexASIO/issues/87
 [issue88]: https://github.com/dechamps/FlexASIO/issues/88
 [logging]: README.md#logging
+[FlexASIO_GUI]: https://github.com/flipswitchingmonkey/FlexASIO_GUI
 [official TOML documentation]: https://github.com/toml-lang/toml#toml
 [portaudio287]: https://app.assembla.com/spaces/portaudio/tickets/287-wasapi-interprets-a-zero-suggestedlatency-in-surprising-ways
 [PortAudioDevices]: README.md#device-list-program
diff --git a/FAQ.md b/FAQ.md
index 77d52ad0..a5c10ca3 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -28,6 +28,13 @@ The reason for the lack of a proper control panel is because developing a
 graphical user interface requires a lot of time and resources, which FlexASIO
 currently doesn't have.
 
+That said, third-party FlexASIO GUIs do exist:
+
+- flipswitchingmonkey's [FlexASIO GUI][FlexASIO_GUI]
+- Nam-K's [FlexASIO configuration helper][FlexASIO_ConfigGUI]
+- [Room EQ Wizard][REW] provides a custom control
+  panel when FlexASIO is used as the ASIO driver
+
 ## Why does FlexASIO fail to initialize?
 
 There are many reasons why FlexASIO might refuse to initialize. Sadly, the ASIO
@@ -261,12 +268,15 @@ available but then fail to initialize when that sample rate is selected.
 [channels]: CONFIGURATION.md#option-channels
 [device]: CONFIGURATION.md#option-device
 [CONFIGURATION]: CONFIGURATION.md
+[FlexASIO_GUI]: https://github.com/flipswitchingmonkey/FlexASIO_GUI
+[FlexASIO_ConfigGUI]: https://github.com/Nam-K/FlexASIO_ConfigGUI
 [logging]: README.md#logging
 [issue #3]: https://github.com/dechamps/FlexASIO/issues/3
 [issue66]: https://github.com/dechamps/FlexASIO/issues/66
 [issue87]: https://github.com/dechamps/FlexASIO/issues/87
 [PortAudio]: http://www.portaudio.com/
 [report]: README.md#reporting-issues-feedback-feature-requests
+[REW]: https://www.roomeqwizard.com/
 [sampleType]: CONFIGURATION.md#option-sampleType
 [suggestedLatencySeconds]: CONFIGURATION.md#option-suggestedLatencySeconds
 [wasapiAutoConvert]: CONFIGURATION.md#option-wasapiAutoConvert
diff --git a/README.md b/README.md
index 7d892225..c12bf03d 100644
--- a/README.md
+++ b/README.md
@@ -52,6 +52,8 @@ The default settings are as follows:
  - 20 ms "preferred" buffer size
 
 All of the above can be customized using a [configuration file][CONFIGURATION].
+You might want to use a third-party tool such as flipswitchingmonkey's
+[FlexASIO GUI][FlexASIO_GUI] to make this easier.
 
 For more advanced use cases, such as low-latency operation and bit-perfect
 streaming, see the [FAQ][].
@@ -133,6 +135,7 @@ while the problem is occurring, and attach it to your report. The output of
 [DirectSound]: https://en.wikipedia.org/wiki/DirectSound
 [Etienne Dechamps]: mailto:etienne@edechamps.fr
 [FAQ]: FAQ.md
+[FlexASIO_GUI]: https://github.com/flipswitchingmonkey/FlexASIO_GUI
 [file an issue]: https://github.com/dechamps/FlexASIO/issues/new
 [GitHub]: https://github.com/dechamps/FlexASIO
 [GitHub issue tracker]: https://github.com/dechamps/FlexASIO/issues