Roadmap

Updating Website and Knowledgebase

We’re improving the PeekShot website and knowledgebase to make information easier to find, understand, and use. Expect clearer documentation, better examples, and a smoother overall browsing experience.

Add feature to hide cookie banner, ads and popups

Currently some websites shows cookie banners, ads or popups which obstructs the clearity of captured screenshot. There should be an option to remove all this disturbance to capture a clean screenshot without any cookie banner or ads.

Bulk Screenshots

User should be able to provide a csv of urls and can capture all screenshots in bulk and get back the screenshot urls in the result csv and also get this output csv on email.

In built scheduling feature for capturing recurring screenshots

User can now provide a url they like to capture, and can choose the capture frequency from daily, weekly and monthly. And can see the all captures of that url in timeline view.

Disable Animations

Turn off page animations during capture to get clean, consistent screenshots without motion blur or flickering elements.

Use Case:
Disable CSS transitions so pop-ups, sliders, or animated banners don’t interfere with your product screenshots.

Ability to delete screenshots from a project to free storage

At least manually. If possible, also via the API, so we can use an automation to instruct the deletion of past screenshots (or move them in a different folder) before taking new ones

Complete revamp of PeekShot Dashboard

Revamped complete dashboard for better user experience

Html to Image Support

Submit html via API and get an image from it. Not a URL, but raw html rendered as an image.

Use case: get an image of a html formatted email

Credit Usage Clarity

It would be helpful to have more clarity around credit usage. There doesn’t appear to be a record of what each screenshot is costing in credits, and there’s no “statement” showing usage over time. It would be amazing if credit usage could be more clear, even better if this could be returned in API calls too.

Lazyloading support

Website that lazy load their images aren’t being screenshotted correctly because the lazy loaded elements aren’t being triggered.

Wait for Element to Load

Ensure screenshots are captured only after a specific element on your page has fully loaded, so you never miss dynamic content.

Use Case:
Use this to wait for a pricing table or a banner loaded via JavaScript before taking a screenshot, avoiding blank or incomplete captures.

Emulate Device

Preview how your website looks on different devices like mobile phones or tablets by simulating their screen sizes and behaviors.

Use Case:

You can capture how your landing page appears on an iPhone 14 to ensure mobile users see the right layout and content.

Inject Custom CSS and JS

Users can inject custom CSS and JavaScript into a webpage before capturing a screenshot, enabling them to alter the page's appearance or behavior for testing, styling, or automating certain interactions during the capture process.

Multiple API Keys

It would be great to be able to have an API key per project.

Use case:

I might use Peekshot with my clients to be able to show examples of their site. They might use Peekshot to take those screenshots. Having a separate API key mean that They could use the api without any fear of them seeing the other projects that I have set up

Support for Custom Header

User can pass custom header while capturing screenshot via dashboard or api.