Use 1024px thumbnail instead of full-size original in receipt preview by justinpersaud · Pull Request #87163 · Expensify/App

justinpersaud · 2026-04-06T14:10:59Z

Explanation of Change

The wide RHP loads receipt images with fillSpace={true}, which sets shouldUseThumbnailImage to false in ReportActionItemImage. This caused the component to load the full-size original receipt image instead of the 1024px thumbnail (.jpg.1024.jpg).

Cloudflare analytics show full-size receipt originals (~800KB avg) account for ~75% of all receipt image bandwidth (~12 TB/week at peak). The 1024px thumbnail (~140KB avg) is more than sufficient for the wide RHP viewport (typically rendered at ~400px wide). Users can still access the full-size original by opening the receipt in the full-screen lightbox, which uses a separate code path (TransactionReceiptModalContent) unaffected by this change.

This change always uses thumbnailSource (the 1024px variant) for inline receipt previews, regardless of the shouldUseThumbnailImage flag.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/620914

Tests

Open an expense with a receipt image attached
Verify the receipt displays correctly in the wide RHP (expense detail panel)
Open DevTools Network tab, filter by "receipts"
Verify the image URL ends in .jpg.1024.jpg (1024px thumbnail), not .jpg (full-size original)
Click the receipt to open the full-screen lightbox
Verify the lightbox loads the full-size original (URL ending in .jpg)
Verify the receipt renders correctly in chat previews (TransactionPreview)

Verify that no errors appear in the JS console

Offline tests

N/A — receipt images already show a loading state when offline. This change only affects which URL is requested.

QA Steps

Open an expense with a receipt image attached (Reports -> Expenses -> Click on any expense with a receipt)
Verify the receipt displays correctly in the wide RHP
Click the receipt to open the full-screen lightbox and verify it loads the full-size image
Verify receipt thumbnails display correctly in chat previews and search results

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

MacOS: Chrome / Safari

Verified via Playwright browser automation:

Wide RHP loads .jpg.1024.jpg (1024px thumbnail) ✓
Full-screen lightbox loads .jpg (full-size original) ✓
No visual regressions in receipt display ✓

The wide RHP was loading full-size original receipt images (~800KB avg) instead of 1024px thumbnails (~140KB avg) when viewing expense details. This was caused by the shouldUseThumbnailImage flag being false when fillSpace is true, which made the source fall through to the original image URL. Always use the thumbnail source for inline receipt previews; full-size originals are still loaded when opening the full-screen lightbox.

melvin-bot · 2026-04-06T14:11:37Z

@deetergp Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

github-actions · 2026-04-06T14:32:44Z

🚧 @justinpersaud has triggered a test Expensify/App build. You can view the workflow run here.

luacmartins · 2026-04-06T18:50:21Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

luacmartins · 2026-04-06T18:52:29Z

PR Author Checklist / checklist (pull_request_target) is failing, but we don't need to block on that.

github-actions · 2026-04-06T18:53:09Z

🚧 @luacmartins has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-04-06T18:58:12Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #87163.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-3d700e9-e41257d-e146cacef1d697f61ce47fd9713ae49d2de3865f/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-3d700e9-e41257d-e09547a475b8c1ee1268961362513a8e92a379c1/index.html

Web 🕸️
https://87163.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-04-06T19:01:13Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2026-04-07T01:27:18Z

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.3.53-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	failure ❌
🍎 iOS 🍎	failure ❌

Bundle Size Analysis (Sentry):

Android

MelvinBot · 2026-04-07T01:28:40Z

No help site changes are required for this PR.

This change is a performance optimization that switches inline receipt previews from loading full-size originals to 1024px thumbnails. It doesn't affect any user-facing behavior, UI labels, settings, or workflows — users still see receipts in the same places and can still open full-size images in the lightbox.

I reviewed all receipt-related articles under docs/articles/ and none reference image resolution or loading behavior. The existing documentation describes user actions (uploading, cropping, attaching receipts) which are unaffected by this change.

OSBotify · 2026-04-07T01:38:14Z

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.3.53-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	failure ❌
🍎 iOS 🍎	failure ❌

Bundle Size Analysis (Sentry):

Android

OSBotify · 2026-04-07T23:55:53Z

🚀 Deployed to production by https://github.com/roryabraham in version: 9.3.53-7 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

justinpersaud requested review from a team as code owners April 6, 2026 14:11

melvin-bot Bot assigned justinpersaud Apr 6, 2026

melvin-bot Bot requested review from JmillsExpensify and deetergp and removed request for a team April 6, 2026 14:11

justinpersaud added the Ready To Build label Apr 6, 2026

This comment has been minimized.

Sign in to view

justinpersaud requested review from luacmartins and mountiny April 6, 2026 16:18

luacmartins approved these changes Apr 6, 2026

View reviewed changes

luacmartins merged commit 3d700e9 into main Apr 6, 2026
44 of 52 checks passed

luacmartins deleted the jpersaud/fix-receipt-image-size branch April 6, 2026 18:52

OSBotify mentioned this pull request Apr 7, 2026

Deploy Checklist: New Expensify 2026-04-07 #87187

Closed

96 tasks

MelvinBot mentioned this pull request Apr 14, 2026

Steph's chat with Melvin #87829

Closed

mountiny mentioned this pull request Apr 22, 2026

Revert "Use 1024px thumbnail instead of full-size original in receipt preview" #88512

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Use 1024px thumbnail instead of full-size original in receipt preview#87163

Use 1024px thumbnail instead of full-size original in receipt preview#87163
luacmartins merged 1 commit into
mainfrom
jpersaud/fix-receipt-image-size

justinpersaud commented Apr 6, 2026 •

edited

Loading

Uh oh!

melvin-bot Bot commented Apr 6, 2026

Uh oh!

github-actions Bot commented Apr 6, 2026

Uh oh!

This comment has been minimized.

luacmartins commented Apr 6, 2026 •

edited

Loading

Uh oh!

luacmartins commented Apr 6, 2026

Uh oh!

Uh oh!

github-actions Bot commented Apr 6, 2026

Uh oh!

github-actions Bot commented Apr 6, 2026

Uh oh!

OSBotify commented Apr 6, 2026

Uh oh!

OSBotify commented Apr 7, 2026

Uh oh!

MelvinBot commented Apr 7, 2026

Uh oh!

OSBotify commented Apr 7, 2026

Uh oh!

OSBotify commented Apr 7, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

justinpersaud commented Apr 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot Bot commented Apr 6, 2026

Uh oh!

github-actions Bot commented Apr 6, 2026

Uh oh!

This comment has been minimized.

luacmartins commented Apr 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

luacmartins commented Apr 6, 2026

Uh oh!

Uh oh!

github-actions Bot commented Apr 6, 2026

Uh oh!

github-actions Bot commented Apr 6, 2026

Uh oh!

OSBotify commented Apr 6, 2026

Uh oh!

OSBotify commented Apr 7, 2026

Uh oh!

MelvinBot commented Apr 7, 2026

Uh oh!

OSBotify commented Apr 7, 2026

Uh oh!

OSBotify commented Apr 7, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

justinpersaud commented Apr 6, 2026 •

edited

Loading

luacmartins commented Apr 6, 2026 •

edited

Loading