White labelling serves Pictor from your own domain, in your own colours, with your logo. It applies to your whole account, not to individual events. Important - White labelling is part of the Enterprise add-on, which sits on top of whichever plan you are on. It is not included in Basic, Pro or Premium on their own. And unlike most things in Pictor it is not something an event switches on for itself — it applies to your whole account and is arranged with us. Talk to us before you start. What you need - An Enterprise plan - A domain you own, with access to its DNS - A SendGrid account, if you want delivery email to come from your domain White label settings: your domain, your colours, your logo. White label settings: your domain, your colours, your logo. Step 1 — Add your domain 1. Go to Whitelabel. 2. Enter your domain in Custom domain — host name only, no https:// and no path. For example booth.yourcompany.com. 3. Save. 4. Copy the CNAME target shown on the page. 5. In your DNS provider, add a CNAME record pointing your subdomain at that target. Set TTL to 3600 or Auto. Step 2 — Turn on HTTPS 1. Back on the Whitelabel page, click Provision SSL. 2. Wait for the status to read SSL valid. DNS changes take time to spread. If you see "The certificate request failed. Check the CNAME record and try again.", your record has probably not reached us yet — wait and try again. Save the domain before you provision. Pictor will tell you if you have not: "Save a custom domain first." Once a certificate exists, the domain is locked. To change it, click De-provision SSL first. Step 3 — Connect SendGrid So that delivery email comes from your domain rather than ours: 1. Create a SendGrid account and complete Sender Authentication. 2. Add SendGrid's DNS records to your provider. 3. Generate an API key with full access. 4. Enter the SendGrid details on the Whitelabel page. Verify your sender address in SendGrid first. It will not send from an unverified sender. Step 4 — Add your branding Title appears in the browser tab and the sidebar. Logo — PNG or JPG. It displays best at around 100×40 px. Use Choose from library to pick one you have already uploaded. Colours — each has a defined job: | Colour | Where it shows | | -------------------- | ------------------------------------------ | | Primary | Primary actions — Create New, Edit, Launch | | Secondary | Secondary actions | | Accent | Navigation and state indicators | | Title | Page titles and section headers | | Background | The main app background | | Inner background | Cards and content panels | | Table header | Table header rows | | Success | Confirmations | | Danger | Destructive actions and errors | Change Primary first and look at the Events list — it carries most of the visual identity. Reset to defaults puts them all back. Step 5 — Test it Open your custom URL and check: - It loads over HTTPS with no security warning - The camera works - Your branding appears - A test email arrives from your sender address Removing a white label Deleting one releases the certificate and stops the custom domain resolving. Everyone on that domain falls back to Pictor branding, so anyone with a bookmark loses access. Tell your team before you do it. See also - Plans and features — the tiers, and what Enterprise adds - Pricing plans — what each plan costs - Getting around Pictor — where account settings live

Getting Started

Set up a Virtual Booth

A Virtual Booth lets guests run your photo booth experience on their own phone — no app, no account, no physical booth. Important - Virtual Booth makes an event Premium. When to use one - Remote or hybrid events — guests who cannot attend still take part - Client previews — let a client walk the experience before the day - Brand activations — reach people beyond the room - Testing — open it yourself on your phone to check the whole flow Turn it on 1. Open your event and click Output. 2. Expand Virtual Booth and switch it on. Switching Virtual Booth on, and the link guests will use. Switching Virtual Booth on, and the link guests will use. Get the link 1. Open the Launchpad. 2. Under Event access, find Virtual booth. 3. Use Copy link, or Show QR code for this link then Download QR code for print. The link and QR code live on the Launchpad, under Event access. The link and QR code live on the Launchpad, under Event access. Note - If the row shows Off — "Guests cannot reach this yet." — click Turn it on in Output settings. When guests can use it Important - Your event opens and closes on its schedule. There is nothing to launch. Guests arriving outside those times are told: | They see | Because | | ----------------------------------- | -------------------------------------------- | | "This event has not yet started." | Before your start time | | "This event has finished." | After your end time | | "This event is expired!" | Your Max Sessions limit has been reached | Tip - Set the schedule wide enough for a virtual booth. Unlike a physical booth, guests use it whenever they see the link — often well before or after the event itself. Branding it The virtual booth uses your Global Styles. For complete control, use custom HTML in the Virtual Booth output settings. This replaces the standard styling entirely, so you get exact fonts, layouts and sizing — but you are then working outside the normal style settings. What guests do 1. Open the link on their phone. 2. Take a photo with their own camera. 3. Wait while it processes, if your template uses AI. 4. Receive it by whichever sharing methods you enabled. No app, no account. Before you share the link Tip - Open it on your own phone and go all the way through, including delivery. Guests have no operator standing next to them, so anything confusing costs you the session. Tip - Keep the flow short. Every extra stage loses people. Tip - Check your token balance. Virtual captures spend tokens exactly like booth captures, and a link shared widely can go through them faster than you expect. If something is wrong | Problem | Check | | ---------------------------- | -------------------------------------------------------------------- | | The link does nothing | Is Virtual Booth switched on, and is it within the event's schedule? | | Guests see "not yet started" | Your start time | | Guests see "expired" | Your Max Sessions limit | | The camera does not work | The guest must allow camera access in their browser | | Photos do not arrive | See Troubleshooting: Email & Text Delivery |

Getting Started

Creating an AI video

AI Video turns a guest's photo into a short cinematic clip. You set the look once in a template, and every guest gets their own version. AI Video events need a Premium licence to run. You can build and test one on any plan — the licence is checked when the event goes live. Build the template 1. Go to Events and click Create New Event. 2. Name your event and finish creating it. 3. Open the Flow tab, open Choose Experience, and click Add template. 4. Pick your canvas size. 1x1, 16x9 and 9x16 are the usual choices for video. AI outputs support ten aspect ratios: 1:1, 16:9, 9:16, 21:9, 3:2, 2:3, 5:4, 4:5, 4:3, 3:4. The editor tells you if a size is not supported. Add the effect 1. Add a Capture element and set its Output Type to Image. 2. With the capture selected, open its Settings, then Effect → Add effect. 3. Choose AI Video and pick your prompt. 4. Set Quality — Low, Standard or High. Quality changes the token cost, and that cost multiplies by every guest. Token prices are set for your account, so check your own Billing page before a large event rather than relying on a figure from an article. If your prompt uses a reference image added with @, keep that reference in the image prompt only, not the video prompt. If your prompt does not describe camera movement, Pictor applies a slow cinematic motion by default. Override it in the prompt if you want something else. AI Video, added to the capture element. AI Video, added to the capture element. Position it Place the AI output where you want it on the canvas and use Layers to control what sits in front of what. Make the timeline at least as long as the video. Test it 1. Open the Launchpad and click Simulation test. 2. Take a photo and answer any prompt questions. 3. Wait for the render. | Output | Typical render time | | ---------- | ----------------------- | | AI stills | around 37 seconds | | AI videos | 1–2 minutes each | Check the result under Sessions → View Output. Budget that render time into your event plan. At 1–2 minutes a clip a queue builds quickly — see On Screen Delivery for how to keep guests occupied while they wait. Multi-scene videos You can stitch several AI clips into one video. 1. Create a new template. 2. Add Capture 1 with an AI Video Output, then Capture 2 with its own AI Video Output. 3. Set the timeline long enough for both. 4. Hide the captures so only the AI results are visible. 5. Arrange the clips side by side on the timeline. The results stitch into one continuous video. Overlays and blend modes Video overlays add transitions and texture — white flashes, strobes, light leaks. 1. Add a Video Asset to the template. 2. Resize it to match the canvas. 3. Add a Blend Mode and choose Screen. In Screen mode dark areas become invisible and bright areas stay, so a white-flash clip reads as a transition rather than a black box. Adding a video element to a template is itself a Premium feature. On an AI Video event that changes nothing, but bear it in mind if you reuse the technique on a simpler template. Rendering happens in parallel Multiple scenes render at the same time, not one after another. Two one-minute videos take roughly one minute plus stitching, not two. Reviewing the result Go to Sessions and click View Output. You will see each scene, the overlays, and the combined video. See also - Custom AI Prompts — writing the prompt behind it - Plans and features — AI video needs Premium - Pricing plans — what tokens cost

Getting Started

Integrations

Integrations connects Pictor to the outside services your events depend on. | Integration | What it is for | | ------------------ | -------------------------------------- | | SENDGRID | Sending guests their photos by email | | SMS (Twilio) | Sending guests their photos by text | | Dropbox | Backing up captured media | | Stripe Connect | Taking payments with the Paywall stage | | Pictor Api Key | Connecting your own software to Pictor | | Aduvi | Connecting your Aduvi account | Important - Each card has its own toggle, separate from its credentials. Filling in the fields is not enough — switch the card on as well. This is the most common reason delivery silently fails. Email — SENDGRID Optional. Pictor already sends email for you. Connect SendGrid only when you want it to come from your own address instead. Enter your API Key, Sender Email and Sender Name, then switch the card on. NoteVerify your sender address in SendGrid first. SendGrid will not send from an unverified sender. Connect SendGrid to send email from your own address instead of Pictor's. Connect SendGrid to send email from your own address instead of Pictor's. Text messages — SMS (Twilio) Optional. Pictor already sends texts for you. Connect Twilio only when you want them to come from your own number instead. Enter your Twilio sender phone number, SID and AuthToken, then switch the card on. Connect Twilio to send texts from your own number instead of Pictor's. Connect Twilio to send texts from your own number instead of Pictor's. Dropbox 1. Click Connect with Dropbox. 2. Click Authorize and sign in to Dropbox. It then reads Connected with Dropbox. Set the folder per event under Output → Dropbox. Stripe Connect Connect Stripe if you are charging guests with the Paywall stage. Use the same email address as your Pictor account. Pictor Api Key Your key for connecting your own software. Important - New Api Key replaces your existing key. Anything already using the old one stops working immediately. Only generate a new key if you are ready to update everything that uses it. Each integration has its own credentials and its own toggle. Each integration has its own credentials and its own toggle. Important - Use a demo account for screenshots — these cards show live API keys. See also | For | See | | ----------------------------- | ------------------------------------------ | | Delivery not arriving | Troubleshooting: Email & Text Delivery | | Charging guests | Using Paywall | | Sending data to other systems | Using Webhooks |

Getting Started

Analytics

Analytics shows what happened at your events — how many sessions ran, what was created, and how guests shared it. Note - Analytics requires a Pro plan or above. Open it - For one event: open it, and in the Control panel click View analytics. - Across events: click Analytics in the main menu. On a Basic licence, Analytics is locked behind an upgrade. On a Basic licence, Analytics is locked behind an upgrade. What it shows The page is six blocks, top to bottom. Event snapshot Three headline numbers for whatever the filters currently cover: Total Sessions, Total Output and Total Shares & Views. The two export buttons sit directly underneath. The three headline numbers, and the exports that go with them. The three headline numbers, and the exports that go with them. Sessions Three rings. | Ring | What it breaks down | | ------------------- | -------------------------------------------------------------------------------------------------- | | Count by type | Physical (a booth device) against Virtual (a guest's own phone) | | Count by device | Which devices ran the sessions — Windows, iPad, iPhone and so on, named as their owners named them | | Output | What was produced: Photos, AI Photos, AI Videos, Videos | Note - Output counts items, not sessions, so its total is usually higher than the session count. One session can produce several files. Physical against virtual, which devices ran them, and what came out. Physical against virtual, which devices ran them, and what came out. Shares By channel is a bar chart of how guests received their photos. Distribution gives the same split as counts — Email and Gallery are the two that appear most. How guests actually received their photos. How guests actually received their photos. Session data Every session as a row: ID, Timestamp, Status, Sent, Clicked, Shares, Views, and a View link to the content. Sortable by any column, and paginated. Tip - This is the table to open when a guest says they never got their photo. Find their session, and Sent tells you whether Pictor sent it at all. Every session, with whether it was sent, clicked and viewed. Every session, with whether it was sent, clicked and viewed. The Most Viewed / The Most Shared The individual results that travelled furthest, by unique ID, with their view and share counts and a link to each. The results that travelled furthest. The results that travelled furthest. Activity A chart of sessions over time, split Static against Motion and Physical against Virtual. Filtering | Filter | What it shows | | ------------------- | ------------------------------------------ | | Start / End | The date range | | Select Client | One or many clients | | Select Project | One or many projects | | Select Event | One or many events | | Select Device | One or many devices | | Include Virtual | Whether virtual-booth sessions are counted | Click Apply to update. Important - Include Virtual changes your totals. If you are reporting numbers to a client, decide whether virtual sessions should count and keep that consistent between reports. Tip - Filter by client across a date range to see everything you have run for them. This is far more useful in a renewal conversation than a single event's figures. Filter by date, client, project, event and device. Filter by date, client, project, event and device. Exports Two buttons, under the Event snapshot. | Button | What you get | | ---------------- | --------------------------------------------- | | Download ZIP | Every generated file from the events in range | | Download CSV | The numbers behind the page as a spreadsheet | Both respect the filters. Set the range and the client first, then export — otherwise you get everything. Download the media as a ZIP, or the numbers as a CSV. Download the media as a ZIP, or the numbers as a CSV. See also | For | See | | -------------------------- | --------------------- | | Where the counts come from | Launchpad | | What each plan includes | Plans and feature |

Getting Started

Devices, cameras and system requirements

Which Pictor is which There are two pieces of Pictor, and it helps to know which one you are in. | | What it is | Where | | ----------------- | -------------------------------------------------------- | ----------------------------------------------------------- | | Web dashboard | Where you build events, design templates and see results | app.pictor.pro, in any browser | | Booth app | What runs at the venue and takes the photos | App Store and Google Play | Guests need neither. The virtual booth and the public gallery open in any browser, with no app and no account. Web dashboard Any modern browser — Chrome 90+ (best performance), Safari 15+, Edge 90+ or Firefox 90+ — with JavaScript enabled. There is nothing to install. Booth app — iPad iPadOS 16.0 or later. | Model | From | | ------------------ | -------------- | | iPad Pro 11-inch | 2nd generation | | iPad Pro 12.9-inch | 4th generation | | iPad Air | 4th generation | | iPad | 9th generation | | iPad mini | 6th generation | An A13 Bionic chip or newer makes a noticeable difference to AI processing time. Everything works on older supported hardware, but guests wait longer. Booth app — Android Android 7.0 (Nougat) or newer. We recommend 4GB RAM (8GB if you are using AI), 64GB storage, a Snapdragon 865 or equivalent, and an 8MP or better front camera. Android hardware varies a great deal. Test AI output on your actual device before an event rather than assuming it will match an iPad. Using a DSLR DSLR cameras connect through the booth app on iPad, not through the web dashboard. Connect the camera 1. Connect the camera to your iPad by USB and switch it on. 2. In the booth app, open your event and go to Devices. 3. Switch the detected camera ON and wait for it to initialise. 4. In each template, set the camera as the capture source. Preview and capture settings are separate Preview settings control the live view you see on screen. Capture settings control the photo that is actually taken. They can differ, so always take a test photo rather than trusting the preview. Available controls: exposure mode, ISO, aperture, shutter speed, exposure compensation, image quality, white balance and colour temperature, plus autofocus step size and pause duration. Settings that work Set Exposure Mode to Manual (M) so the camera stops changing its mind between guests. A reasonable starting point: ISO 400–800, f/4, 1/125s. Adjust at the venue — lighting is the variable that matters. Set autofocus step size to its lowest value for a faster, smoother capture. Adjusting during an event Triple tap the right side of the screen to reach DSLR settings without stopping the event. When something goes wrong | Problem | Fix | | ----------------------------- | ---------------------------------------------------------------------------------- | | Camera stops responding | Toggle it OFF, wait two seconds, toggle it ON | | No live view | Check the camera is on, the USB cable is firm, and the camera is not in video mode | | Settings greyed out | Switch to Manual exposure mode | | Preview looks dark with flash | Normal — flash fires on capture, not in preview | Carry spare USB cables and a power adapter. Cables are the most common failure at an event. Printing Printing needs the Print Partner App on a Windows or Mac computer connected to your printer. See Printing for setup. Everything needs a connection See Do I need internet for Pictor to work? See also - Do I need internet for Pictor to work? — connectivity - Printing — the Print Partner app - Contacting support — what to send us

Advice and answers from the Pictor.pro Team

Getting Started

Planning Your Event

Features & How-To

Printing & Delivery

Account & Billing

Troubleshooting & FAQ

Drafts

Setting up white label

Set up a Virtual Booth

Creating an AI video

Integrations

Analytics

Devices, cameras and system requirements