diff --git a/guides/howtos/Duration Types with Postgrex.md b/guides/howtos/Duration Types with Postgrex.md
new file mode 100644
index 0000000000..4820185deb
--- /dev/null
+++ b/guides/howtos/Duration Types with Postgrex.md	
@@ -0,0 +1,39 @@
+# Duration Types with Postgrex
+
+As of Ecto 3.12.0, Ecto supports a `:duration` type which maps to Elixir's `Duration` struct (available as of Elixir 1.17).
+
+One natural use case for this is when using Postgres's `interval` type. Historically, Postgrex loads intervals from the database into a custom `Postgrex.Interval` struct. With the introduction of `Duration`, there is now the option to choose between the two. Please follow the steps below to enable mapping to `Duration`.
+
+1. Define your migration
+
+```elixir
+create table("movies") do
+  add :running_time, :interval
+end
+```
+
+2. Define your schema
+
+```elixir
+defmodule Movie do
+  use Ecto.Schema
+
+  schema "movies" do
+    field :running_time, :duration
+  end
+end
+```
+
+3. Define your custom Postgrex type module and specify intervals should decode to `Duration`
+
+```elixir
+# Inside lib/my_app/postgrex_types.ex
+
+Postgrex.Types.define(MyApp.PostgrexTypes, [], interval_decode_type: Duration)
+```
+
+4.  Make Ecto aware of the Postgrex type module in your configuration
+
+```elixir
+config :my_app, MyApp.Repo, types: MyApp.PostgresTypes
+```
diff --git a/mix.exs b/mix.exs
index 5cb4cbd853..1c57bbeb2e 100644
--- a/mix.exs
+++ b/mix.exs
@@ -148,6 +148,7 @@ defmodule Ecto.MixProject do
       "guides/howtos/Composable transactions with Multi.md",
       "guides/howtos/Constraints and Upserts.md",
       "guides/howtos/Data mapping and validation.md",
+      "guides/howtos/Duration Types with Postgrex.md",
       "guides/howtos/Dynamic queries.md",
       "guides/howtos/Multi tenancy with query prefixes.md",
       "guides/howtos/Multi tenancy with foreign keys.md",