Does SwiftShot upload screenshots or page content?
No. Screenshot editing, annotation, redaction, OCR, encryption, and export run locally in your browser. The support form is only for describing issues and should not be used to submit evidence.
FAQ
Quick answers for extension users and legal teams evaluating SwiftShot.
Why does SwiftShot need Chrome permissions?
SwiftShot needs access to the active tab to capture the visible page, scripting for region selection and scroll capture, storage for local settings, and downloads for local exports. It does not use those permissions to read your browsing history or monitor other tabs.
Where are my exports stored?
Exports are saved locally through your browser, usually in Downloads unless you choose another destination. SwiftShot does not keep remote copies.
Can I use SwiftShot without voice commands?
Yes. Voice commands are optional. If you do not want Chrome's SpeechRecognition feature involved, leave voice commands disabled and use the normal buttons and shortcuts.
Should I send a screenshot when asking for help?
No. For privacy, describe the issue in plain language. If the page is sensitive, say what type of page it is without including URLs, names, captured text, or case-specific details.
Install Help
Use the official Chrome Web Store listing whenever possible. After install, pin SwiftShot so it is easy to open during a capture workflow.
1
Install from the Chrome Web Store
Open the SwiftShot listing, choose Add to Chrome, and confirm the extension permissions.
2
Pin the extension
Open Chrome's extensions menu, find SwiftShot, and pin it to the toolbar so capture is one click away.
3
Run a non-sensitive test capture
Test on a public page first. Confirm that capture, annotation, redaction, OCR, and export behave as expected before using it in a real workflow.
Troubleshooting
Most issues come from page restrictions, browser state, or extension permissions. Try these checks before sending a support request.
Capture does not start
Refresh the tab, reopen SwiftShot, and make sure the current page is not a Chrome internal page such as chrome://extensions.
Full-page capture misses content
Dynamic pages can lazy-load as they scroll. Try waiting for the page to finish loading, then rerun the capture.
Export does not appear
Check the browser Downloads shelf and your Downloads folder. Confirm Chrome is allowed to download files on your device.
OCR text looks wrong
Zoom the page to a readable size before capture, avoid blurry source material, and use a crop around the text-heavy region when possible.
Voice commands fail
Voice commands are optional. Check microphone permission and Chrome speech settings, or keep the feature off and use manual tools.
Extension seems stale
Open Chrome extensions, turn Developer mode on, choose Update, then restart Chrome and try a public test page.
Support
Send only enough detail to reproduce the issue. The safest support request contains browser version, extension version, operating system, and a general description of what happened.
- Good to send: browser version, extension version, operating system, general page type, and exact error text if it contains no private data.
- Do not send: captured evidence, screenshots, private URLs, names, passwords, client details, case facts, or sensitive OCR text.