[Android] RNImage resize causes very long images to become blurry

[sookcha]

Description

• RNImage causes very long images to become blurry when resized
• I know it uses Fresco under the hood and Fresco has a limitation of up to 2K resolution, but at least it accepts a configurable max size
• Also recent Android devices can draw much larger than 2K
• I think React Native Image should accept a max size option too
• Or we can update Fresco max size limit

Steps to reproduce

• Load a very large image with RNImage

React Native Version

0.82.1

Affected Platforms

Runtime - Android

Output of npx @react-native-community/cli info

System:
  OS: macOS 26.1
  CPU: (8) arm64 Apple M1 Pro
  Memory: 212.97 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 22.18.0
    path: /Users/hoseongson/.local/share/mise/installs/node/22.18.0/bin/node
  Yarn:
    version: 1.22.19
    path: /usr/local/bin/yarn
  npm:
    version: 10.9.3
    path: /Users/hoseongson/.local/share/mise/installs/node/22.18.0/bin/npm
  Watchman:
    version: 2025.11.10.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /Users/hoseongson/.local/share/mise/installs/ruby/3.3.0/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 25.1
      - iOS 26.1
      - macOS 26.1
      - tvOS 26.1
      - visionOS 26.1
      - watchOS 26.1
  Android SDK: Not Found
IDEs:
  Android Studio: 2025.2 AI-252.25557.131.2521.14432022
  Xcode:
    version: 26.1.1/17B100
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.17
    path: /Users/hoseongson/.local/share/mise/installs/java/corretto-17.0.17.10.1/bin/javac
  Ruby:
    version: 3.3.0
    path: /Users/hoseongson/.local/share/mise/installs/ruby/3.3.0/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 20.0.0
    wanted: 20.0.0
  react:
    installed: 19.1.1
    wanted: 19.1.1
  react-native:
    installed: 0.82.1
    wanted: 0.82.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: Not found
  newArchEnabled: false

Stacktrace or Logs

N/A

MANDATORY Reproducer

https://github.com/sookcha/RnTallImage

Screenshots and Videos

[Abbondanzo]

RN has different resize methods available here that would better suite your needs, such as scale or none. Could you try these out first? https://reactnative.dev/docs/image#resizemethod-android

[sookcha]

Scale doesn't work because the 2K max limit also affects downsampling. I don't think none is an option here because it causes OOM when a large image comes in.

[Abbondanzo]

Fresco can be customized to a higher global maximum dimension with its experimental flag setMaxBitmapDimension, so you could change

react-native/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/fresco/FrescoModule.kt

Line 171 in a5e6add

builder.experiment().setBinaryXmlEnabled(true)

to something like

      builder.experiment().setBinaryXmlEnabled(true).setMaxBitmapDimension(8192)

The only caveat is that would have to be combined with an explicit scale resize method to ensure that the ResizeOptions request parameter is null, otherwise it will overwrite the globally-defined maximum dimension with the default again.

Trying to reduce fragmentation via props as much as possible: would that work for your use cases? Or could you confirm if #54760 works better here

[sookcha]

Trying to reduce fragmentation via props as much as possible

Agreed.

Maybe we could increase the default maxBitMap size to 8192 like Chromium does?

[sookcha]

I opened an issue on Fresco. facebook/fresco#2843

[RyuWoong]

This is a fairly old issue, and it’s unlikely to change. Please consider using another third-party library,
e.g., FastImage, TurboImage.

[sookcha]

@RyuWoong I don't think that's a solution to this issue. I know there are a bunch of third-party libraries out there. At least, we should document this issue so RN users can use a third-party library instead of RNImage, if the issue won't be fixed.

[Abbondanzo]

@RyuWoong do you have any related issues to link to? The last fix #21301 introduced the resizeMethod="none" that I was recommending using here but we can push more fixes into Fresco for maximum bitmap size adjustments

@sookcha since it would be difficult to get a Fresco release in short notice, could you try out setting the custom experiment flag from my snippet above alongside the explicit resizeMethod="scale" to see if it helps? If so, we can get a new ResizeOptions object that doesn't default to the maximum but rather something that can be controlled via RN