Kapture · Prove
Start free: 2,000 tokens →no card. Then TCPA consent recordings as low as $0.001, unlimited e-sign $15/moForms, e-signatures and lead recording.
Every form visit recorded. Every yes kept, word for word.
IN
OUT
Form fillYour Kapture form
Page visitYour site
E-signA document to sign
Embedded formLoads late or from another site
Consent proofExact words, word for word
ReplayRebuilt step by step, not a video
Stored dataYour storage or ours
Lead recordReal IP, record id for buyers
Signed documentReminders and a full trail
Repeat leadBilled once
KaptureForms · E-sign · Lead recordingValidate · Check APIsReady
Saved with Kapture vs. competition – last 30 days Compared with paying the average competitor price for the same certificates.
Consent certificates by Kapture, last 30 days, all customers.
How we figure it: the average of each competitor’s lowest published price per certificate () vs. Kapture’s with your own storage. No customer names. See the comparison.
Explore Kapture: video tour, screenshots, all features and FAQs
The problem, the fix, and the numbers. Then let's talk about what you'd save.
Four ways to add Kapture to your forms, and a signing end to end. Each one filmed inside the running product.
E-signatures with recording
Building forms is free. You pay per record, in flat $0.001 tokens.
Forms
- Describe a form in a sentence and Kapture builds and hosts it
- Or add one script tag to a form you already have
- One pixel per brand, for staging or live
- Mask card numbers and other private fields in the replay
- Start recording on first touch, or only after a consent click
Lead records
- Full session replay: every field, the page, the language. It is rebuilt step by step from what happened, not a video
- The same lead saved twice is billed once
- Tamper-proof proof of submission with the consent wording
- Certified, submitted and abandoned sessions
- Drop-off chart for each form field
- Search by name, email or phone as you type
E-signatures
- Upload a PDF once; Kapture reads its fillable fields, or you place them
- Several signers, automatic reminders
- Full-screen signing on phones, with pinch to zoom, and it works with the phone turned sideways
- Signers can fix a mistake before they sign
- Stages from draft to completed, with full history
- The signing session is recorded
- No seat fee and no envelope cap
Proof for buyers
- A record id (kap_vid) travels with every lead
- Buyers look it up to see the replay and the proof
- Public API key so a dialer can check it automatically
- Share one record by email; the person signs in to watch
Hookups
- Signed webhooks with a test send and a delivery log
- Blacklist check against your own API
- SMS code check through your own provider
- Co-registration: partner pixels, each sees only its own part
- An API, and an MCP connection: ask Kapture in plain words from Claude
Storage
- Your own bucket: R2, S3, B2, Wasabi, Spaces, Telnyx or any S3 endpoint
- Kapture tests the bucket and sets it up for you
- Records stay with you if you leave
- Or KX21-hosted storage, kept 90 days
Questions
- What is Kapture?
- Kapture does three jobs with one pixel: it builds a hosted form from a plain-English description or imports the HTML form you already have, sends documents for e-signature with no per-seat charge, and records what happened when someone submitted, every field, the page they saw and the consent they gave, as a replay plus a tamper-proof proof record kept in storage you own.
- How much does Kapture cost?
- Every token is $0.001, flat, with a $20 minimum purchase, and new accounts start with 2,000 free tokens that never expire, with no credit card needed. With your own storage bucket a completed form is 5 tokens, a lead recording you keep is 1 token, and a signed document is 250 tokens, or $15 a month for unlimited e-signatures. On KX21-hosted storage a submission is 15 tokens and a signed document 750. Building forms is free.
- Is a Kapture recording a video?
- No. Kapture doesn't film the screen, and no video file is made. It saves what happened on the page: the words shown, the fields filled in, the clicks, the scrolling and the timing. When you press play, Kapture rebuilds the visit step by step from those details, so you can watch it back much like a video. Private fields you choose to mask stay hidden in the replay.
- What is the difference between a lead recording and a completed form?
- A lead recording is the session replay and proof for a lead on a form you already run, at 1 token, $0.001, with your own connected storage. A completed form is a form Kapture built and hosts, with the submission and its recording, at 5 tokens, $0.005, with your own connected storage, or 15 tokens, $0.015, on KX21 storage. Both are flat at every volume.
- When does Kapture start recording?
- Not on page load. The pixel opens a session but records nothing until the visitor touches the form you declared for it. If you want recording to wait for something else, such as a consent click, switch the pixel to manual capture and it records only after your page calls startCapture. That is also why an installed tag with no declared form produces empty replays.
- Where are the recordings stored?
- In your own bucket: Cloudflare R2, AWS S3, Backblaze B2, Wasabi, DigitalOcean Spaces, Telnyx storage or any S3-compatible endpoint. Kapture tests the bucket, writes the CORS rule and, on Telnyx, creates it for you. Records stay with you if you leave. KX21-hosted storage is the alternative: records are kept for 90 days and abandoned visits are not kept.
- How does a buyer verify a Kapture record?
- Every certified capture carries an id in a hidden form field, kap_vid, that travels with the lead. Anyone you share with can look that id up to see the replay and the proof, and your dialer can verify it automatically with your API key. You can also share one submission by email; the person signs in to watch it.
- Can Kapture push each lead to my systems?
- Yes. A webhook on the pixel receives every captured lead as a signed POST with an HMAC secret you hold, with a test delivery and a delivery log per webhook. A blacklist check against your own API can tag a lead before it is forwarded, and an SMS verification step through your own provider can confirm the phone number on the form.
- Does Kapture mask sensitive fields?
- Yes. Point it at the page and it inspects the form in a headless browser, identifies the fields and their types, and writes the pixel's mask policy from what it finds, so card numbers and other sensitive inputs are masked in the replay. It also reports whether the tag is actually installed and a form is declared.
- Can I see where visitors abandon a form?
- Yes. Sessions are classed as certified, submitted with a real recording, or abandoned. For abandoned sessions the drop-off funnel shows how many reached each field in order, so you can see which question loses people. Keeping the abandoned recordings themselves is optional, 1 token each on your own bucket.
- Does Kapture support co-registration?
- Yes. A master pixel records your opt-in page and carries a list of partner pixels. Each partner sees only its own hop and the master's; the master sees the whole chain for one visitor, across several pages or on one page. Partners connect by invitation and can revoke the connection at any time.
- Does e-signature cost per seat?
- No. A signed document is $0.25 pay as you go, however many people sign it, or $15 a month for unlimited e-signatures with a verified bucket of your own. Templates are built from an uploaded PDF with mapped fields, support several signers, send automatic reminders, and can record the signing session as one more Kapture capture.
- Does Kapture replace TrustedForm?
- For proof of consent on your own forms, it records the same thing and keeps it in your bucket. Tamper-evident consent records are not a category Kapture invented, and no tool can promise a TCPA outcome.



