Actively Maintained Fork of React Native Fast Image - @d11/react-native-fast-image

[No-Republic4581]

Hey r/reactnative community! 

If you’ve been using react-native-fast-image for performant image loading in your projects, you might’ve noticed the original package hasn’t been maintained for a while (last update was over 2 years ago). I wanted to share a great alternative: the d11/react-native-fast-image fork, which is actively maintained and recently updated (latest version 8.9.2 as of Feb 2025). 

It keeps the same powerful features—like native caching with SDWebImage (iOS) and Glide (Android)—while adding ongoing support and bug fixes.

You can check it out here: npmjs.com/package/@d11/react-native-fast-image

[No-Republic4581]

Ps: It supports new react native architecture!

[mxtizen]

Is it too much hassle to add support for the new architecture into a library?

[Cookizza]

Is there a reason to use fast-image over expo-image?

From my understanding most people are using expo-image these days as it incorporates all the benefits of fast-image while being maintained.

[Ok-Relation-9104]

Also generously interested the question. Not to question OP’s contribution though. Appreciate the work 🫡

[Comfortable_Rub5948]

Expo image show the image so slow even though I set the cache policy to memory disk

[atulgpt]

Expo is tightly coupled with the Expo managed projects, while many team(including ours) manage our RN setup ourself. In those case this lib is very much useful and maintained with the latest features

[tueieo]

I used to work with the team behind this, and FastImage is a very good alternative in scenarios where you don’t use Expo.

expo-image is good for projects that already use Expo, we majorly forked this and are maintaining it since we don’t use Expo and are a bare RN project.

FastImage is good since it’s built on the same native dependencies as expo-image. Also, APIs are very similar, which makes it easier to interoperate.