diff --git a/docs/assets/20250204_versionstream.png b/docs/assets/20250204_versionstream.png
new file mode 100644
index 0000000..2f3130d
Binary files /dev/null and b/docs/assets/20250204_versionstream.png differ
diff --git a/docs/assets/20250204_weekly.png b/docs/assets/20250204_weekly.png
new file mode 100644
index 0000000..4038c33
Binary files /dev/null and b/docs/assets/20250204_weekly.png differ
diff --git a/docs/index.md b/docs/index.md
index 3811fab..43b617d 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -15,10 +15,10 @@ We refer to data *directly consumable by analyses* as ***analysis-grade data***
 *NiPreps* were conceived as a generalization of *fMRIPrep* across new modalities, populations, cohorts, and species.
 *fMRIPrep* is widely adopted, as our telemetry with Sentry (and now, *in-house* with [migas](https://github.com/nipreps/migas-py)) shows:
 
-| ![fmriprep usage](assets/20250102_weekly.png) |
+| ![fmriprep usage](assets/20250204_weekly.png) |
 |:--:|
 | *fMRIPrep* is executed an average of 11,800 times every week, of which, around 7,800 times it finishes successfully (66.2% success rate). The average number of executions started includes debug and *dry* runs where researchers do not intend actually process data. Therefore, the *effective* (that is, discarding test runs) success ratio of *fMRIPrep* is likely higher. |
 
-| ![fmriprep versions](assets/20250102_versionstream.png) |
+| ![fmriprep versions](assets/20250204_versionstream.png) |
 |:--:|
 | Streamplot of *fMRIPrep*'s version adoption. |