diff --git a/README.md b/README.md
index 3b03b0e..b081df9 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@
 and formats. It supports:
 
 * setting defaults
-* reading from JSON, TOML, and YAML config files
+* reading from JSON, TOML, YAML and HCL config files
 * live watching and re-reading of config files (optional)
 * reading from environment variables
 * reading from remote config systems (etcd or Consul), and watching changes
@@ -31,7 +31,7 @@
 
 Viper does the following for you:
 
-1. Find, load, and unmarshal a configuration file in JSON, TOML, or YAML.
+1. Find, load, and unmarshal a configuration file in JSON, TOML, YAML or HCL.
 2. Provide a mechanism to set default values for your different
    configuration options.
 3. Provide a mechanism to set override values for options specified through
@@ -72,7 +72,7 @@
 ### Reading Config Files
 
 Viper requires minimal configuration so it knows where to look for config files.
-Viper supports JSON, TOML and YAML files. Viper can search multiple paths, but
+Viper supports JSON, TOML, YAML and HCL files. Viper can search multiple paths, but
 currently a single Viper instance only supports a single configuration file.
 Viper does not default to any configuration search paths leaving defaults decision
 to an application.
@@ -266,7 +266,7 @@
 
 `import _ "github.com/spf13/viper/remote"`
 
-Viper will read a config string (as JSON, TOML, or YAML) retrieved from a path
+Viper will read a config string (as JSON, TOML, YAML or HCL) retrieved from a path
 in a Key/Value store such as etcd or Consul.  These values take precedence over
 default values, but are overridden by configuration values retrieved from disk,
 flags, or environment variables.