
Use a Shuffle node after Natron's Read node to select the layer containing the PDF page you need. A multipage PDF is not necessarily exposed as an animation in which advancing the playhead selects the next page. The Natron 2.5 Read guide explicitly describes PDF page selection through layers.
Key Takeaways
- PDF page content and animation frame time are different axes.
- Select the desired page layer downstream of Read.
- Verify the visible page identity before transforming or compositing it.
Check what the Viewer is showing
Load a working copy of a permitted PDF, then inspect the Read output. Note a distinctive heading, page number or illustration on the visible page. Move the playhead only as a diagnostic: if the page does not change, do not conclude that Natron discarded the other pages.
Insert Shuffle after Read and inspect the available layers. Choose the layer corresponding to the required page and send that result to the Viewer. Confirm the visible content against the source document rather than assuming a layer's order matches a printed page label.
Build one deliberate page branch
For a compositing task, keep the Read node as the shared document input and give each needed page a clearly named selection branch. For example, a title-card branch and a diagram branch should each identify which visible page they represent.
This is an editorial organization proposal, not a claim that all PDF features survive import. Fonts, transparency and vector artwork should be checked in the rendered image before delivery. If the selected page does not resemble a trusted PDF viewer, stop and create an explicitly reviewed raster source through a suitable document-rendering workflow.
Proposed example: a cover and an inside diagram
Suppose a short explainer uses the cover of a PDF and a diagram from an interior page. First select the cover layer and verify its title. Then create a separate page-selection branch for the diagram and verify its caption. Only after those identities are correct should you animate their placement.
Write the source document name, visible page heading and intended shot into the handoff notes. This protects the editor from substituting an adjacent page that happens to have a similar layout. The physical-page versus page-label guide explains why printed numbering alone is weak identification.
Keep page extraction separate from image extraction
A PDF page is a composed layout. An embedded photograph within that page is a different source object. If the requirement is the whole page, compare the complete rendered page. If the requirement is one embedded image, use an appropriate extraction workflow rather than cropping a low-resolution preview and calling it the original.
For acceptance, reopen the project copy, select each intended branch, and compare its visible page identity with the approved source. Inspect the final frame size and important text at the delivery scale. The PDF render-versus-extract guide helps decide which source you actually need.
Related tasks
- Why Does PDF Page 1 Appear as Page 5 in the Viewer?
- How Do I Take the Correct Scanned Page from a PDF for Image Editing?
- How Does Photopea Turn a Multi-Page PDF into an Editable PSD Layout?
Sources and scope
- Natron2.5 official documentation: Read imports multipage PDFs; a downstream Shuffle selects the layer containing a desired page.
Documentation-based guidance for Natron 2.5 manual and named built-in node; later2.6 not assumed. Examples are proposed checks, not reported tests. Official source bodies were read on2026-10-23; user-discussion evidence is not search-volume or AI-citation-frequency data.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Paparazzi Ratzfatzzi / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.