diff --git a/doc/images/load-balancing.png b/doc/images/load-balancing.png
new file mode 100644
index 0000000000000000000000000000000000000000..18b68bfdad83d15b33f37eeeb98f582feb8ee0c0
Binary files /dev/null and b/doc/images/load-balancing.png differ
diff --git a/doc/load-balancing.md b/doc/load-balancing.md
index 4ed938c990373a0d9fe5898a143083800f84b693..c5e59331c2da4ef9f574d066110dcfa042040597 100644
--- a/doc/load-balancing.md
+++ b/doc/load-balancing.md
@@ -96,7 +96,7 @@ Load-balancing policies fit into the gRPC client workflow in between
 name resolution and the connection to the server.  Here's how it all
 works:
 
-![image](images/load-balancing.svg)
+![image](images/load-balancing.png)
 
 1. On startup, the gRPC client issues a [name resolution](naming.md) request
    for the server name.  The name will resolve to one or more IP addresses,