diff --git a/README.md b/README.md
index 3b3315f..f020c69 100644
--- a/README.md
+++ b/README.md
@@ -129,9 +129,13 @@ for (uint32_t m = 0; m < t->mip_levels; m++) {
 yapf_tex_free(t);
 ```
 
-The language bindings and the JavaScript port speak version 1; the C
-library's v1 functions also read 8-bit version 2 files (2D, cube face 0,
-array layer 0), so plugins built on them open those too.
+Every extension opens version 2 files: GIMP (at full 16-bit / float
+precision, faces and frames as layers), Blender (HDR as float images),
+KDE and Linux thumbnails, VS Code (with face / layer / frame / slice
+pickers), Figma and Photoshop.  The Python binding (`yapf.load_texture`)
+and the JavaScript port (`YAPF.decodeTexture`) read every texture; the
+other bindings wrap the v1 functions, which also read 8-bit version 2
+files (2D, cube face 0, array layer 0).
 
 ---
 
diff --git a/docs/LANGUAGES.md b/docs/LANGUAGES.md
index 17df03f..06ab3f0 100644
--- a/docs/LANGUAGES.md
+++ b/docs/LANGUAGES.md
@@ -22,13 +22,14 @@ the same native code, so they are all about equally fast; the JavaScript
 port needs no native library at all.  Every example also re-encodes the
 image and checks that the result is byte-identical to the original file.
 
-**YAPF 2 textures.**  The bindings wrap the version 1 API (`yapf_load`,
+**YAPF 2 textures.**  Most bindings wrap the version 1 API (`yapf_load`,
 `yapf_save`, …).  Through it they also read 8-bit version 2 files (2D, or
 face 0 / layer 0 of cubes and arrays).  GPU blocks, 16-bit / float pixels,
 volumes and the other version 2 features are available from C and C++
 through the `yapf_tex_*` functions in [`yapf.h`](../yapf.h) (see
 [FORMAT.md](FORMAT.md)); any language with a C FFI can call them the same
-way.  The JavaScript port reads and writes version 1 only.
+way.  Python (`yapf.load_texture`) and JavaScript (`YAPF.decodeTexture`)
+read every version 2 texture; the JavaScript port writes version 1.
 
 ## Getting the native library