diff --git a/Monitor-Troubleshooting.md b/Monitor-Troubleshooting.md
new file mode 100644
index 0000000..8a577bb
--- /dev/null
+++ b/Monitor-Troubleshooting.md
@@ -0,0 +1,46 @@
+We often get issues like:
+ _"MonitorControl doesn't work with my monitor"_,  
+so here are some troubleshooting steps and general information to try and help you.
+
+# General Information
+* MonitorControl **doesn't work with every monitor**, it all depends on how well your display/cable manufacturer implements the [DDC/CI spec](https://en.wikipedia.org/wiki/Display_Data_Channel).
+* Some displays will only support certain features well (for example, they work well with brightness but not volume).
+* It also depends a lot on your [hardware combination](https://github.com/the0neyouseek/MonitorControl/issues/82).
+
+# Troubleshooting
+
+## I can't control volume/brightness
+### Try a different ddc tool
+First step you can try is a different ddc tool called [ddcctl](https://github.com/kfix/ddcctl).  
+If your setup works with ddcctl it should also work with MonitorControl.  
+After installing ddcctl, try something like:
+```sh
+./ddcctl -d 1 -v 30
+```
+(tries to set the volume of display 1 to value 30)
+or 
+```sh
+./ddcctl -d 1 -b 30
+```
+(tries to set the brightness of display 1 to value 30)
+
+If these commands change your brightness or volume, you know that your display supports ddc (or at least the command that worked).
+
+### Try a different cable
+If the first step didn't work for you, your next best bet is trying a different cable/connection.
+
+Generally, people seem to have the highest succes rates with DisplayPort and the lowest with HDMI.
+
+## I can't get accurate read values from the monitor
+If monitor is unable to read the values from the display, it will default to the last known values.
+
+To try and fix this, you can try checking the `Longer Delay` option inside `Preferences > Advanced`.  
+See the [Advanced Preferences](https://github.com/the0neyouseek/MonitorControl/wiki/Advanced-Preferences#longer-delay) wiki page for more information.
+
+## The app is slow on startup
+This is usually because we poll the display to try and read its current volume/brightness on app launch. 
+
+You can lower or disable the `Polling Mode` inside `Preferences > Advanced`.  
+See the [Advanced Preferences](https://github.com/the0neyouseek/MonitorControl/wiki/Advanced-Preferences#polling-mode) wiki page for more information.
+
+