How to Take Scrolling Screenshots on iPhone 13 Without Full-Page Option
Learn why Full Page is missing on iPhone 13 and how to save long webpages, stitch screenshots, or record scrolling content.
Quick answer: On iPhone 13, press and quickly release the Side button and Volume Up button together. If Full Page appears in the screenshot preview, choose it. Apple shows this option for supported content such as an entire webpage in Safari. If Full Page is missing, there is no Apple-documented switch that forces one long still image in every app. Use Safari’s PDF workflow, capture overlapping screenshots and stitch them, or record the scroll as a video instead.
1. Take a normal screenshot first
- Open the webpage, document, chat, or app screen you want to capture.
- Scroll to the point where the capture should begin.
- Press and quickly release the Side button and Volume Up button at the same time. Do not hold them; holding buttons can open the power-off or emergency screen.
- Tap the thumbnail that appears in the lower-left corner to open the screenshot preview. These button steps are documented by Apple Support.
At this point you have a normal screenshot of the visible screen. The preview is also where iOS places the Full Page control when the current content supports it.
2. Use Full Page when iOS offers it
- Look at the top of the screenshot preview for Screen and Full Page tabs.
- Select Full Page.
- Use the right-side preview or the scroll bar to inspect the captured content.
- Crop if needed, then save. Depending on the content and iOS workflow, you can save the result as an image or PDF.
Full Page is context-dependent. Apple’s documentation uses an entire Safari webpage as its example; it does not promise that every third-party app, feed, conversation, or embedded view exposes the option. The iPhone 13 itself is not necessarily missing a capability just because the tab is absent.
3. Why the Full Page option is not showing
- The current app does not expose a supported long-document view. Many apps render content in a custom scroll view, canvas, feed, or paginated interface that iOS cannot automatically extend.
- You are capturing a screen rather than a document. Full Page is intended for supported over-screen content, with Safari webpages as Apple’s documented example.
- The content is inside a frame or embedded browser. An in-app browser may not provide the same capture controls as Safari.
- The page has not finished loading. Wait for images, text, and dynamic sections to appear, then take the screenshot again.
- The preview was dismissed. Take another screenshot and immediately tap its thumbnail; the Full Page control is part of the preview workflow.
There is no universal setting that turns Full Page on for every app. Choose the output you actually need: a long still image, a PDF, or a video of the scroll.
4. Save a long Safari webpage as a PDF
For a webpage, PDF is usually the cleanest built-in replacement for a missing Full Page image.
- Open the page in Safari and wait for it to finish loading.
- Tap the Share button.
- Choose Markup. iOS creates a PDF preview of the webpage.
- Tap Done, then choose Save File To.
- Select iCloud Drive or a folder on your iPhone and tap Save.
Apple documents this workflow in Annotate and save a webpage as a PDF in Safari. A PDF preserves selectable text and page structure, but it is not the same as one tall PNG or JPEG.
5. Create a long image by stitching screenshots
When you need an image of app content, take several overlapping screenshots and combine them in an image editor or stitching app.
- Start at the top of the content and take a screenshot.
- Scroll down by less than one screen height so the next frame overlaps the previous one. Keep a recognizable line, image edge, or other landmark in both frames.
- Repeat until you reach the end. Keep the same orientation and zoom level throughout.
- Import the frames into an editor that supports vertical stitching or place them on a tall canvas manually.
- Align the overlapping landmarks, remove duplicate areas, and export as PNG or JPEG.
Stitching tips
- Use consistent scroll increments; irregular jumps make alignment harder.
- Dismiss floating buttons, keyboards, cookie prompts, and chat bubbles before capturing when possible.
- Do not pinch-zoom between frames.
- For a page with lazy-loaded images, pause after each scroll so images finish loading.
- Keep the original screenshots until you have checked the final composite for missing or duplicated content.
6. Record the scroll as a video
If a still image is not required, screen recording preserves the act of scrolling.
- Open Control Center by swiping down from the top-right corner.
- Tap the Screen Recording button. If it is not present, add it in Settings → Control Center.
- Wait for the three-second countdown, then scroll through the content at a readable speed.
- Open Control Center and tap the recording button again, or tap the red status indicator and choose Stop.
- Find the recording in Photos and trim the beginning or end if needed.
Screen recording captures video, not a single long still. Apple notes that some apps may block recording of their content; see Apple’s screen-recording guide.
7. Choose the right method
| Need | Best option | Trade-off |
|---|---|---|
| Long Safari page with selectable text | Share → Markup → Save File To | Produces a PDF, not a tall image |
| Long image of app content | Overlapping screenshots and stitching | Manual alignment and cleanup |
| Show motion or interaction | Screen Recording | Video instead of a still image; some apps restrict recording |
| Supported webpage in screenshot preview | Full Page | Only appears for content that iOS supports |
8. Or skip the browser setup
If the source is a public URL rather than your iPhone’s private app screen, ScreenshotNeo can capture the webpage through one API request. It cannot capture an iPhone app screen, but it is useful when you need repeatable website images or PDFs without configuring a browser.
See the ScreenshotNeo API documentation for all options. Basic request examples:
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server includes take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Start with a free ScreenshotNeo account.
9. Troubleshooting checklist
| Problem | Likely cause | Fix |
|---|---|---|
| Nothing happens when pressing buttons | Buttons were held too long or not pressed together | Quickly press and release Side and Volume Up at the same time. |
| Full Page is absent in Safari | The preview was closed, page is still loading, or the view is unsupported | Reload, wait for content, take a new screenshot, and open the thumbnail immediately. Use the PDF workflow if it remains absent. |
| Only the visible screen is saved | Screen tab remained selected | Select Full Page before saving; otherwise use PDF or stitching. |
| Stitched image has jumps | Scroll increments changed or frames have no overlap | Retake with smaller, consistent movements and clear landmarks. |
| Images are missing in the long capture | Lazy loading had not completed | Pause after each scroll and confirm images are visible before the next screenshot. |
| Screen recording will not start | Recording control is not in Control Center or the app restricts capture | Add Screen Recording in Control Center settings; if the app blocks it, use screenshots or its export feature. |
10. Quality, privacy, and file-size notes
- For readable text, keep the phone at its normal zoom and avoid sending a compressed messaging copy as your master file.
- A very tall stitched image can be difficult to view and share. Split it into sections when a service imposes pixel or file-size limits.
- Review captures for private messages, account numbers, addresses, and notification banners before sharing.
- PDF is preferable for archiving and searching text; PNG or JPEG is preferable when a design or visual layout must be preserved.
- For repeatable public webpage captures, an API avoids manual scrolling and gives you a consistent URL-based workflow. It does not replace screenshots of private, logged-in iPhone apps.
FAQ
Can I enable Full Page for every app?
No. Apple documents Full Page for supported content, with an entire Safari webpage as the example. Apps decide how their content is exposed to the screenshot workflow.
Does iPhone 13 support scrolling screenshots?
It supports the Full Page option when the current content provides it. The option is not guaranteed for every screen.
Can I save a scrolling screenshot directly as a JPEG?
When Full Page is available, iOS determines the available save formats in that workflow. For a guaranteed image output from app content, stitch overlapping screenshots and export PNG or JPEG.
What is the fastest way to preserve a long Safari article?
Use Share → Markup → Save File To and keep it as a PDF. Use stitching only when you specifically need a single image.
Why is a video sometimes better than a long image?
A recording preserves animation, interactions, and the path through content. It is unsuitable when someone needs a static image or searchable document.
