Free online tools that run in your browser
Your files never leave your device · No login required · 100% free
Convert, compress, calculate, generate, edit and check files right in your browser — fast, private and easy to use.
Search results
Popular tools
View all toolsBrowse by category
Popular file conversions
View all convertersProgramming
Learn and practise programming in your browser. Pick a language: write code, run it in a real terminal and follow the lessons step by step.
Why Shiklo Tools?
Simple, private tools that just work — right in your browser.
- Private Everything runs in your browser. Files are never uploaded.
- Secure Encrypted HTTPS connection, and nothing you open is stored on our servers.
- No login required No account, no sign-up, no email. Just open a tool and use it.
- Fast No upload or download wait — results appear instantly.
- Free All tools are free to use, with no limits.
- Works everywhere Phone, tablet or computer, in any modern browser.
🆕 New tools
★ Popular tools
Recently used
Frequently asked questions
Are my files or text uploaded anywhere?
No. Every tool runs inside your browser on your own device. Nothing you enter or open is sent to a server.
Do I need to create an account or log in?
No login is required. There are no accounts — open any tool and start using it straight away.
Are the tools really free?
Yes. All tools are free, with no limits or watermarks. The site is supported by ads.
Does it work on my phone?
Yes. The tools work in any modern browser on phones, tablets and computers.
Can I use the tools offline?
Once a tool has loaded it does its work on your device, so it keeps working even if your connection drops.
Which file types are supported?
PDF, Word, Excel, PowerPoint, OpenDocument and RTF documents, JPG, PNG, WebP, HEIC, AVIF, GIF and BMP images, MP4, MOV, WebM and MKV videos, MP3, WAV, M4A, OGG and FLAC audio, ZIP, 7z, RAR, TAR and GZIP archives, CSV, JSON, XML and plain text. Each tool lists exactly what it opens.
All tools with descriptions →
Permissions-Policy Generator
Build the Permissions-Policy header that turns off the camera, microphone, location and other browser features your site doesn't use.
Modern browsers give web pages access to powerful features: the camera and microphone, location, payments, USB and Bluetooth devices, screen sharing, the clipboard and motion sensors. Most sites use few of them. The Permissions-Policy header lets you switch off everything you don't use, for your own pages and for anything embedded in them — so even if a third-party script or an injected iframe tries to turn on the microphone, the browser refuses.
This generator lists two dozen features with plain-language descriptions. For each, choose Off, This site only, This site plus specific origins, or Allowed everywhere — or press one button to turn off everything except a few harmless features. The header is built as you go, ready to copy into your server, CDN or hosting configuration. Nothing is sent anywhere.
How to use Permissions-Policy Generator
- Press Turn off everything I don't use for a strict start.
- Allow the features your site needs, for your site or for named origins.
- Copy the Permissions-Policy header.
- Add it to your server, CDN or hosting settings and check it with the Security Headers Checker.
Features
- Camera, microphone, location, payment, USB, Bluetooth, serial and more.
- Off, this site only, this site plus origins, or everywhere.
- One-click strict preset.
- Valid header syntax (structured fields).
- Plain-language description of every feature.
- Runs in your browser; nothing is sent.
How the header works
Each feature gets an allowlist. An empty list switches the feature off everywhere; self allows it on your own pages; quoted origins allow it in iframes from those sites as well. Features you leave out keep the browser's default, which usually allows your own pages and blocks cross-origin iframes.
| Setting | Header syntax | Effect |
|---|---|---|
| Off everywhere | camera=() | No page or frame can use the camera |
| This site only | geolocation=(self) | Only your own pages may ask for location |
| This site + origins | payment=(self "https://pay.example") | Your pages and that payment frame |
| Allowed everywhere | fullscreen=* | Any page or frame may use it |
Frames need both sides
For an embedded frame to use a feature, two things must allow it: your Permissions-Policy header must include the frame's origin, and the iframe tag needs an allow attribute, such as allow="payment; fullscreen". The header sets the outer limit — a frame can never get more than the page allows. That is why switching features off at the top level is such an effective safeguard.
Common choices
A typical content site turns off the camera, microphone, location, payment, USB, serial, Bluetooth, HID, MIDI, sensors and the Topics API, and allows fullscreen, picture-in-picture and clipboard writing for its own pages. A video-calling app allows the camera, microphone and display capture for itself. A shop allows payment for itself and its payment provider's frame. The strict preset gives you the content-site version to start from.
Browser support
Permissions-Policy replaced the older Feature-Policy header and is supported by Chromium-based browsers such as Chrome and Edge. Other browsers support parts of it or ignore it; the header never causes errors, so sending it is safe everywhere. Some features in the list are newer or experimental, and browsers ignore names they don't recognise.
Related tools
Combine this header with a Content-Security-Policy from the CSP Generator, check what your site sends with the Security Headers Checker, and publish a security contact with the security.txt Generator.
Frequently asked questions
Does the header stop third-party scripts using the camera?
Yes. With camera=() no script or frame on the page can turn the camera on.
Should I turn off the Topics API?
If your site doesn't rely on interest-based ads, turning it off is a simple privacy improvement.
What is the Permissions-Policy header?
An HTTP header that controls which browser features your pages and embedded frames may use.
How do I disable the camera and microphone?
Set camera and microphone to Off; the header will contain camera=() and microphone=().
What replaced Feature-Policy?
Permissions-Policy, with a slightly different syntax.
Will the header break my site?
Only if you switch off a feature your site uses — allow those for your own site.
How do I allow a feature in an iframe?
Add the origin in the header and an allow attribute on the iframe.
Where do I add the header?
In your web server, CDN or hosting configuration, as a response header.
Is anything sent to a server?
No. The header is built in your browser.
Related tools
CSP GeneratorBuild a Content-Security-Policy header or meta tag from a strict starting point, and check any policy for common weaknesses.
Security Headers CheckerCheck a website's HTTP security headers — HSTS, CSP, X-Frame-Options, Referrer-Policy and more — get a grade and how to fix each gap.
security.txt GeneratorCreate a valid security.txt file (RFC 9116) so researchers know how to report vulnerabilities — with checks for every field.
SRI Hash GeneratorCreate Subresource Integrity hashes (sha384 and more) for scripts and stylesheets, with the ready script or link tag to paste.
Meta Tag GeneratorGenerate the title, meta description, canonical, robots, Open Graph and Twitter / X tags for a page, with Google and social previews.
Robots.txt Generator & TesterCreate a robots.txt with rules per crawler, AI crawler blocking and sitemap lines, then test any URL against any robots.txt file.