diff --git a/README.md b/README.md
index 06f9e720ca7f..d9648ec8296e 100644
--- a/README.md
+++ b/README.md
@@ -229,6 +229,7 @@ Whenever you change dependencies (adding, removing, or updating, either in `pack
 - [Developing on MetaMask](./development/README.md)
 - [How to generate a visualization of this repository's development](./development/gource-viz.sh)
 - [How to add new confirmations](./docs/confirmations.md)
+- [Browser support guidelines](./docs/browser-support.md)
 
 ## Dapp Developer Resources
 
diff --git a/docs/browser-support.md b/docs/browser-support.md
new file mode 100644
index 000000000000..aac357bdfe36
--- /dev/null
+++ b/docs/browser-support.md
@@ -0,0 +1,14 @@
+# Browser Support
+
+MetaMask's browser support policy is to support:
+
+* The last two years of Chrome stable releases
+* The current and previous Firefox Extended Support Release
+
+We try to support browser forks as well (aligned with supported Chrome/Firefox releases), but we don't actively test them.
+
+## Providing notice of minimum supported version changes
+
+Additionally, before bumping our minimum supported browser versions, we should always notify users in the application first. Otherwise users of older browser versions would unknowingly get stuck on old MetaMask versions, even if they had automatic updates enabled.
+
+We have a home screen notification already for this purpose. All we need to do us update the `OUTDATED_BROWSER_VERSIONS` constant in the release prior to the minimum version bump, and all affected users should be notified in-app.