Repository navigation
docs: screenshot and PDF links expire after 7 days - #155
Merged
Merged
Conversation
Generated screenshot and PDF URLs are now signed and valid for 7 days. Updates the example URLs and replaces the 'public and durable' wording with download guidance.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
junhsss
approved these changes
Nov 6, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Screenshot and PDF URLs returned by
/v1/screenshot,/v1/pdfand/v1/scrapeare now signed and expire after 7 days. This updates the Browser Tools overview to match:images.steel.dev/v1/static/artifacts/<token>/<id>.pngfor screenshots andfiles.steel.dev/...for PDFs. The old example also had the wrong host for screenshots.Links issued before the change keep working.
Merge timing
Merge this once the API change is live in production, not before.