Frequently asked questions
Common questions
about Kaptr.me.
Short answers about capture, refresh, protected websites, sharing and the data Kaptr.me stores.
Back to documentation ↑01What is Kaptr.me and how does it work?
Kaptr.me lets you capture the useful part of a website and keep that visual information inside a dashboard. The browser extension performs the capture, sends the snapshot you chose to save to Kaptr.me, and can refresh it later from the browser session that performs the refresh.
02Can I share my Kaptr.me dashboard with others?
Yes. Dashboards are private by default. You can switch to Shared to grant access only to invited Kaptr.me accounts, or Public when you want a public link. Public visibility and search-engine indexing are separate choices.
03How does snapshot refresh work?
For local refresh, Kaptr.me asks the extension in the browser doing the refresh to reopen the source and capture the saved area again. It uses that browser's current local session, so protected pages depend on the session available on the device performing the refresh.
04Does Kaptr.me work on sites where I need to be signed in?
Yes, when the browser performing the local capture or refresh is already signed in to that source. If another computer or browser is signed out, that protected source cannot be refreshed from that session.
05Does Kaptr.me store my source-site login details?
Local capture and refresh do not require Kaptr.me to receive your source-site passwords or browser authentication session. Those credentials remain with the local browser session used to access the source.
06What data is sent to Kaptr.me?
When you save a capture, the snapshot itself and the information needed to manage it in your dashboard are sent to Kaptr.me. Your local browser authentication session remains local. AI features use a separate processing flow described on the Security and Privacy pages.
