I get this error:
\nKeyError: 'screenshot@fullPage'

Could someone please clarify this inconsistency?

I figured this out on my own.

\n
• In order to get a screenshot of the top part of a website, the format option should be specified as \"screenshot\".
\n
• In order to get a full page screenshot, the format option should be specified as \"screenshot@fullPage\".
\n
• Either way, to get the screenshot link, the print request must be always:
  \nprint(page_content['screenshot'])
  \nAnd the link will direct you to the screenshot, which is of the entire page or just the top section, depending on what you put as a format option.
\n

Is full page screenshot supported? #633

Answered by ifx-querido

ifx-querido asked this question in Q&A

Is full page screenshot supported? #633

ifx-querido

Sep 6, 2024 · 2 comments · 3 replies

Answered by ifx-querido Return to top

Discussion options

ifx-querido

Sep 6, 2024

According to the welcome page of the V1 documentation , the fullpage screenshot is an existing option for the scrape function. Additionaly, @nickscamara just posted a new announcement about the V1, which includes the fullpage screenshot as an added feature. However, the Advanced Scraping Guide only lists ["markdown", "links", "html", "rawHtml", "screenshot"] as output formats. And when I try to run: page_content = app.scrape_url(website, { "formats": ['markdown', 'screenshot@fullPage'], }) print(page_content['screenshot@fullPage']) I get this error: KeyError: 'screenshot@fullPage' Could someone please clarify this inconsistency?

1 You must be logged in to vote

Answered by ifx-querido Sep 9, 2024

I figured this out on my own.

• In order to get a screenshot of the top part of a website, the format option should be specified as "screenshot".
• In order to get a full page screenshot, the format option should be specified as "screenshot@fullPage".
• Either way, to get the screenshot link, the print request must be always:
  print(page_content['screenshot'])
  And the link will direct you to the screenshot, which is of the entire page or just the top section, depending on what you put as a format option.

View full answer

Replies: 2 comments · 3 replies

Comment options

ifx-querido

Sep 9, 2024

Author

I figured this out on my own. In order to get a screenshot of the top part of a website, the format option should be specified as "screenshot". In order to get a full page screenshot, the format option should be specified as "screenshot@fullPage". Either way, to get the screenshot link, the print request must be always: print(page_content['screenshot']) And the link will direct you to the screenshot, which is of the entire page or just the top section, depending on what you put as a format option.

Marked as answer

1 You must be logged in to vote

2 replies

Comment options

robertnowell Feb 17, 2025

what is the difference between format and actions with respect to screenshot? in node: const crawlResponse = await firecrawl_app.scrapeUrl(url, { formats: ["markdown", "html", "screenshot@fullPage"], actions: [{ type: "screenshot", fullPage: true }], }); what is the difference between formats and actions for getting a screenshot?

Comment options

mogery Feb 20, 2025

Maintainer

what is the difference between format and actions with respect to screenshot? screenshot@fullPage format always runs after all actions. With the screenshot action, you can take multiple screenshots in between e.g. clicking buttons. The results will be in actions.screenshots in the response.

Answer selected by ifx-querido

Comment options

robertnowell

Feb 20, 2025

thank you! very helpful. Is this explained in depth in the documentation somewhere? I didn’t understand from reading through the main docs Find me on LinkedIn <http://www.linkedin.com/in/robert-nowell>, Github <https://github.com/robertnowell> … On Wed, Feb 19, 2025 at 10:33 PM Gergő Móricz ***@***.***> wrote: what is the difference between format and actions with respect to screenshot? ***@***.*** format always runs after all actions. With the screenshot action, you can take multiple screenshots in between e.g. clicking buttons. The results will be in actions.screenshots in the response. — Reply to this email directly, view it on GitHub <#633 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AET7YAB6Q34VYYVVRYXEU5T2QVZM7AVCNFSM6AAAAABNYIG3UCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRVHA4DCMI> . You are receiving this because you commented.Message ID: ***@***.***>

1 You must be logged in to vote

1 reply

Comment options

mogery Feb 20, 2025

Maintainer

Just extended the API reference to show this info on the actions Screenshot tab as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Category

🙏

Q&A

Labels

None yet

3 participants