# Apollo client cache issues when working with heavy media data **URL:** \ **Category:** MCP Server\ **Created:** [February 2, 2026, 10:30pm UTC](https://community.apollographql.com/t/apollo-client-cache-issues-when-working-with-heavy-media-data/9682 "2026-02-02T22:30:21Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![kuala886](https://avatars.discourse-cdn.com/v4/letter/k/e95f7d/32.png) [@kuala886](https://community.apollographql.com/u/kuala886)\ **Post date:** [February 2, 2026, 10:30pm UTC](https://community.apollographql.com/t/apollo-client-cache-issues-when-working-with-heavy-media-data/9682/1 "2026-02-02T22:30:21Z")
Hey folks, I’m running into something odd when using apollo client with large media-heavy graphql responses. When I pull in project data for things like [pc video editing](https://cepcutapk.com/capcut-for-pc/), the cache seems to bloat quickly and sometimes stale fragments get reused, which leads to mismatched UI states after mutations. Has anyone dealt with cache invalidation or pagination strategies for big binary-style metadata? Also curious if there are best practices to keep memory usage and network traffic under control when the data model gets this heavy. ---
**Author:** ![discourse\_ai\_spam](https://avatars.discourse-cdn.com/v4/letter/d/c68b51/32.png) [@discourse\_ai\_spam](https://community.apollographql.com/u/discourse_ai_spam)\ **Post date:** [February 2, 2026, 10:30pm UTC](https://community.apollographql.com/t/apollo-client-cache-issues-when-working-with-heavy-media-data/9682/2 "2026-02-02T22:30:32Z")
Unlisted on February 2, 2026, 10:30pm UTC ---
**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/system/32/5529_2.png) [@system](https://community.apollographql.com/u/system)\ **Post date:** [February 3, 2026, 7:01pm UTC](https://community.apollographql.com/t/apollo-client-cache-issues-when-working-with-heavy-media-data/9682/3 "2026-02-03T19:01:31Z")
Listed on February 3, 2026, 7:01pm UTC