Changelog What’s new in urlshot.io.

New options, fixes and changes to the screenshot API and the dashboard, each dated the day it reached production.

Follow the RSS feed to hear about each one as it ships.

October 2026

  1. NewAPI

    Capture one element of a page

    The new selector parameter captures a single element, such as a pricing table, a chart or an embedded post, instead of the whole viewport.

    Read more: Capture one element of a page

  2. ChangedAPI

    Timeouts and failed page loads keep their error codes

    A render that times out now returns render_timeout, and a page that can’t be loaded navigation_failed, instead of both arriving as render_failed.

    Read more: Timeouts and failed page loads keep their error codes

  3. ChangedAPI

    Screenshots wait for late content by default

    The default for wait_until is now auto, which waits for content that arrives after the page has loaded, so fewer screenshots come back half empty.

    Read more: Screenshots wait for late content by default

  4. FixedAPI

    First requests after a quiet spell no longer time out

    A request that arrives while the browser is still starting now waits for it, instead of failing with render_timeout after timeout_ms plus five seconds.

    Read more: First requests after a quiet spell no longer time out

September 2026

  1. NewDashboard

    Sign in with Google

    Create an account or sign in with your Google account, and manage how you sign in from Settings.

    Read more: Sign in with Google

  2. ImprovedAPI

    Browsers keep embedded screenshots

    Screenshots now carry a Cache-Control header that follows cache_ttl, so a page that embeds one doesn’t fetch it again on every view.

    Read more: Browsers keep embedded screenshots

  3. NewAPI

    Send screenshot options as JSON

    You can now POST to /v1/screenshot with a JSON body, with the same options, limits, price and cache as a GET request.

    Read more: Send screenshot options as JSON

  4. ImprovedAPI

    A header naming the build that took a screenshot

    Each screenshot now carries X-Urlshot-Renderer, naming the browser build that produced it, to quote if you contact support.

    Read more: A header naming the build that took a screenshot

  5. ImprovedDashboard

    Request logs show how each request authenticated

    Each request in the dashboard’s request log now says whether it used your secret key or a signed URL.

    Read more: Request logs show how each request authenticated

  6. NewDocumentation

    Code examples in Ruby, Java, C# and Go

    The quickstart and the signed-URL examples now come in seven languages, with Ruby, Java, C# and Go alongside Node.js, Python and PHP.

    Read more: Code examples in Ruby, Java, C# and Go

  7. NewAPI

    Custom CSS and JavaScript before the capture

    New custom_css and custom_js options change the page before the screenshot, to hide an element, open a tab, or wait until your content is ready.

    Read more: Custom CSS and JavaScript before the capture

  8. NewWebsite

    Try the API on the home page, no account needed

    The home page has a live demo that takes any public URL and returns a real screenshot, without signing up.

    Read more: Try the API on the home page, no account needed

  9. NewAPI

    Signed URLs for screenshots in an img tag

    Put a screenshot straight into a web page with a signed URL, without exposing your secret key.

    Read more: Signed URLs for screenshots in an img tag

  10. NewAPI

    The urlshot.io screenshot API is live

    One request turns a public URL into a PNG, JPEG or WebP screenshot, rendered in Chromium, with a Free plan to build against.

    Read more: The urlshot.io screenshot API is live

Request a new feature.

Tell us what you’d like the API to do, and what you’d use it for. We read every request and weigh each one when deciding what to build next.