PlainCapture – Screen Recorder, Screenshot & Video Editor extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: akcpipibnhkglmkgebmagfdpnhhoklcc
Permissions (5)
- Execute scripts in pages
- Capture tab content
Related extensions
Full Page Screenshot, Screen Capture & Recorder – SnapScreenProductivity
Full Page Screenshot & Screen Recorder – No Watermark by SuperchargeBrowserProductivity
Screen Recorder & Screenshot - Record a Tab with No Login or WatermarkProductivity
PageShot - Full Page ScreenshotProductivity
ClarShot: Screenshot & Screen RecorderProductivity
Plainrec – Screen Recorder, No LimitsProductivity
Frequently asked questions
Is PlainCapture – Screen Recorder, Screenshot & Video Editor safe to use?
Our latest automated scan rates the Chrome listing of PlainCapture – Screen Recorder, Screenshot & Video Editor at 80/100 (some risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does PlainCapture – Screen Recorder, Screenshot & Video Editor require?
PlainCapture – Screen Recorder, Screenshot & Video Editor requests 5 permissions. The most significant: Execute scripts in pages, Capture tab content. See the full breakdown in the security report.
Who develops PlainCapture – Screen Recorder, Screenshot & Video Editor?
PlainCapture – Screen Recorder, Screenshot & Video Editor is published by PlainCapture. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 1.3.1
- Current listed version
- 1.3.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 0 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.