Live filters that run on your phone, photos saved to your OpenVibe.Pics, private cameras you share by the week, and a one-tap still from any stream.
One script and one tag: the same preview, filters, timer and burst, in any page you make. Nothing starts until someone taps, and the picture stays in the browser unless you ask Cam to save it to Pics. This one is live: try it.
The element, its events and the API<script src="https://openvibe.cam/embed/ov-camera.js" async></script>
<ov-camera filters="none,warm,vivid"></ov-camera>The cam button takes the frame OpenVibe.Media already serves, saves it to your OpenVibe.Pics as a still with your caption, and hands the chat line back to Live. Nothing is recorded and nothing is analysed.
How the cam button calls Cam
Live · exampleChat a still is posted to the stream
Pair a phone, a Pi or an IP camera you own. Its wall is private; you name one viewer, choose a week, and revoke it at any time. The next request is refused — there is no cached copy of a grant.
Pair a cameraA private cameraExample grant · Raspberry PiThe camera app runs the colour, light and blur on your device. The picture goes to OpenVibe.Pics; Cam keeps the link and the filter name, never the bytes.
Take a photoExample · Warm · saved to PicsNoneMonoWarmCoolFadeVividSoftNo. A camera is private to its owner. A viewer sees its wall only while a grant you gave is active, and a revocation is checked on every read. v1 has no public directory.
In OpenVibe.Pics, as your own pictures. Cam stores the Pics slug and links, the filter name and your caption — never the image bytes.
No. There is no face recognition, no identity classification and no AI analysis of a picture. Filters are colour and light, applied in your browser.
It calls Cam with your own Network token. Cam fetches the live frame from OpenVibe.Media, saves it to your Pics as a still and returns the line Live posts in the stream chat.