FlatList removeClippedSubviews default on Android with Fabric

Direct Answers

Does removeClippedSubviews default to false on Android when Fabric is enabled? No official source confirms this. The legacy Android default remains true, and Fabric’s documentation does not state a different default. The safest working assumption is that the default stays true unless you override it.

Is enabling it on Android 13 safe for production FlatLists? No public crash reports exist, but there are no documented guarantees either. Fabric’s view detachment and recycling differ from the legacy renderer, so behavior can diverge across devices and OS versions.

Should teams explicitly set removeClippedSubviews={false} until Fabric behavior is documented? Yes. Explicitly disabling it gives predictable performance and avoids relying on an undocumented default that may change in future releases.

Confirmed Facts vs. Likely Explanation

Confirmed	Likely / Inferred
React Native 0.66 changed the iOS default to false; Android legacy default stayed true.	Fabric retains the legacy Android default (true) because no release notes or docs mention a change.
Fabric is still marked experimental in the latest stable release.	Fabric’s view recycling may handle clipped subviews differently, making the legacy true behavior unreliable or suboptimal.
No official documentation states a Fabric-specific default for removeClippedSubviews on Android.	Future releases could flip the default or alter the prop’s effect without a major version bump.

Recommended Action

1. Add removeClippedSubviews={false} to every FlatList (or VirtualizedList) used on Android when Fabric is enabled.
2. If you need the memory savings of clipped-subview removal, test explicitly with removeClippedSubviews={true} on your target device matrix before shipping.
3. Pin the React Native version in package.json and re-verify the behavior after every upgrade.

Verification Steps (Run Once Per Project)

# 1. Create a minimal test project
npx react-native@latest init FabricClipTest --template react-native-template-typescript
cd FabricClipTest

# 2. Enable Fabric (RN 0.76+)
echo 'newArchEnabled=true' >> android/gradle.properties

# 3. Add a FlatList that logs the effective prop value
# App.tsx
import { FlatList, View, Text, useRef, useEffect } from 'react-native';

export default function App() {
  const listRef = useRef<FlatList<string>>(null);
  useEffect(() => {
    // @ts-ignore - internal prop for debugging
    console.log('effective removeClippedSubviews:', listRef.current?.props?.removeClippedSubviews);
  }, []);
  return (
    <FlatList
      ref={listRef}
      data={Array.from({ length: 200 }, (_, i) => `Item ${i}`)}
      keyExtractor={(_, i) => String(i)}
      renderItem={({ item }) => (
        <View style={{ padding: 20, borderBottomWidth: 1, borderColor: '#ccc' }}>
          <Text>{item}</Text>
        </View>
      )}
      // removeClippedSubviews intentionally omitted
    />
  );
}

# 4. Build and run on Android 13 emulator/device
npx react-native run-android

# 5. Observe the log output (Metro console or logcat)
# Expected: "effective removeClippedSubviews: true" (legacy default)
# If you see "false", the default has changed—document it and adjust your explicit setting.

One Diagnostic Detail That Changes the Recommendation

If your verification step shows removeClippedSubviews resolving to false by default on Android with Fabric, you can stop explicitly setting false—but you should still document the observed version and re-check on every upgrade.