Inspect the join, the cloud setting and the file that will actually leave your phone
A stitched screenshot can make a conversation, document or long page easier to review, but a neat-looking seam is not proof that the content is complete. Scrollum's official listing describes automatic matching, manual adjustments and a cloud fallback setting whose default matters. This source-based guide explains a cautious review workflow; it does not report a hands-on stitching or privacy test.
For an independent professional sending a reference to a client, the useful goal is a readable and appropriately limited record. That means checking what was captured, how the join was made and what the exported image reveals. The app can support those steps, while the responsibility for the final handoff remains with the person sharing it.
What it does
Start by deciding which material belongs in the reference. Capture overlapping screenshots that preserve the necessary context and keep the originals. Avoid collecting unrelated private messages or account details simply because they happen to sit near the relevant passage. A narrower input can make both matching and later privacy review easier.
Scrollum describes automatic overlap detection that applies a match only when it is verified against the originals. Uncertain content remains available for review rather than being silently treated as a reliable overlap. That boundary is useful, but it does not mean every resulting stitch is complete. A repeated header or similar-looking line can still require careful comparison with the captures.
For manual work, the app supports ordering images, cropping the top or bottom, dragging a join and moving it by one pixel. Undo, redo and zoom give routes for inspecting and reversing changes. Vertical and horizontal stitching are described, along with direct joining when images do not overlap. Use the route that reflects the actual inputs rather than forcing unrelated images into an apparent continuous page.
Before you install
Before automatic matching, inspect Cloud Matching Fallback in Settings. The official description says it is on by default. Matching begins locally, but on supported devices and systems a reduced grayscale version may be sent to Apple Private Cloud Compute when local assessment remains unresolved and verifiable candidates exist. Turning the fallback off is the documented way to prevent that optional matching route.
Reduced grayscale is not the same as anonymous. Text, names and distinctive content can remain visible in a smaller monochrome image. Decide whether the captures are appropriate for that processing path before proceeding. The developer describes stitching, editing and export as local; that does not erase the separately stated cloud fallback boundary.
Review each join against the originals. Check that a sentence, amount or label has not vanished between the upper and lower image. Look for duplicated lines as well as missing ones, since either can change how a reference is interpreted. Inspect a difficult transition at a useful zoom level and make a small manual correction only when the original content supports it.
Then review the whole image as a reader would encounter it. Confirm that the sequence is in the intended order and that cropping has not removed context needed to understand a statement. A continuous image should not imply that two unrelated captures were one uninterrupted original document. Where the relationship is ambiguous, explain it in the accompanying message.
Price and access
The free tier permits three images per task and includes the stated automatic and manual stitching and export functions. A one-time Pro purchase raises the limit to twenty images per task, without a subscription. The description does not establish a current US dollar price for that purchase, and image-size or processing limits still apply.
Count the inputs for the actual task before starting a large reference. Splitting work into separate outputs can be clearer than building a very long image that no recipient can comfortably read. The app describes no account registration and watermark-free export, but neither statement replaces checking the current access screen and final file.
Our take
Export options include PNG and JPEG, size controls, saving to Photos and sharing through other apps. Inspect the actual exported file before sending it. Check legibility, the first and last lines and any private information that was outside the useful subject. An editing preview and a delivered file are different stages of the handoff.
The qualified recommendation is a sequence of decisions: limit the capture, choose the cloud setting, verify the joins, review context and inspect the export. Scrollum documents tools for those steps without promising that every stitch or privacy choice is automatically correct. A good reference preserves the meaning of its source and gives the recipient only the information they need.
A client reference should also explain what the image represents. If it combines several captures, say so rather than allowing the uninterrupted shape to imply a single original screenshot. That small accompanying note can preserve trust while the stitched copy provides the convenience of reading the relevant material in one place. Keep the source captures available for comparison.
