ZUQ

Explain this document to me as a video

225 modules, one bar each

Some documents you have to understand rather than read: a chapter before the exam on it, a policy you are about to be held to, a spec you have to build against, a set of notes someone else wrote, a contract waiting for your signature. ZUQ is built to take the document you upload, ask what you need from it, and plan a narrated video that explains those parts in plain words, at the level you already have.

This is an early build, and this is what happens to the document itself. You can attach up to 5 files, each with your own one-line note. An image is resized in your browser and uploaded to storage only our build worker can read. A PDF or a text file is never uploaded - its text is read in your browser, and only that text travels with your request, where the model that plans your course reads it.

No course video is generated yet - a finished build hands you a sample file, not your course. What follows is what the product is being built to do, stated plainly. A request made today is saved, and we will tell you the day that changes.

Make a video

StatusEarly build: we save your request and plan the course. No course video is generated yet - a finished build hands you a sample file, not your course - and we will tell you the day that changes.

A document video walkthrough is a narrated video, planned from a document you upload and what you say you need from it, that explains those parts in plain words at the level you already have and names where in the document each point came from.

What you can hand over

The content track treats the document as the syllabus. Whatever it is, the walkthrough is planned from it and from what you say you need, rather than from a general course on the subject.

What the picker takes

PNG, JPEG, WebP and GIF images, PDF, plain text and Markdown, and nothing else - a format that is not on that list is refused at the picker rather than halfway through a build. Up to 5 files, each under 10 MB, and at most 20,000 characters are read out of any one PDF or text file.

A photograph of a page counts: hand over a picture of the worksheet or the clause and it is treated as content the same way a PDF is.

How the video is planned

You say what you need to know, the way you would say it out loud. The plan follows that question, not the table of contents. If you need one section, the walkthrough goes to that section. If you need the whole thing, it is taught in order, start to finish, and takes as long as that honestly takes.

A document walkthrough is built to open by mapping the source, put the key definitions in plain words, work through the passages your question points to, say what the source assumes you already know, and end with a short recall set so you can check what stayed.

The chapter titles are decided by the build worker when your job starts, from your own words and from whatever text it was handed. The shape named here is the fallback it uses when that call does not come back - not a list you are promised, and not one you approve before the build begins.

Pitched at the level you have

Before anything is planned, you say how much you already know, and the walkthrough is pitched there. Beginner assumes nothing and builds every idea from first principles, in order. Intermediate assumes the vocabulary and moves at working pace. Advanced assumes the formalism and goes straight at the hard parts. Expert assumes the literature: no recap, no analogies.

Minutes are the only meter, and a build costs exactly the runtime it produces: a 15-minute walkthrough spends 15 minutes of your monthly allowance. The content track opens at 15 minutes and the ladder runs to 30 hours. The pricing page lists what each plan grants and what a top-up adds.

When the document is a contract

When the document is something you are about to sign, the walkthrough names clauses rather than chapters: the clause that sets the price and how it changes, the notice period and its date, the cap on liability and what sits outside it, the exclusivity clause. The contract to video page walks that flow step by step.

We are not your lawyer and this is not legal advice. This is so that when you do talk to your lawyer, you already know which three pages to talk about.

Where this build stands

Four things are true of this build today, and each one is shown in the flow rather than in a footnote.

Early build: we save your request and plan the course. No course video is generated yet - a finished build hands you a sample file, not your course - and we will tell you the day that changes.

You can attach up to 5 files, each with your own one-line note. An image is resized in your browser and uploaded to storage only our build worker can read. A PDF or a text file is never uploaded - its text is read in your browser, and only that text travels with your request, where the model that plans your course reads it.

Payments are live. A plan is a recurring monthly subscription and a top-up is a one-time charge, both taken through Stripe Checkout, and your card details never reach ZUQ.

Early build: an update request spends real minutes and hands back another sample file, not your rendered course. The video you have now is kept exactly as it is, and we will tell you the day real rendering begins.

Questions

Can I upload a PDF and have it explained to me as a video?

That is what ZUQ is being built to do: upload the document, say what you need from it and how much you already know, and get a narrated walkthrough of those parts in plain words. In this early build no course video is generated yet - a finished build hands you a sample file, not your course. Your request is saved, and we will tell you the day that changes.

Does it explain the whole document or just the part I ask about?

The parts your question points to, in the order you need them. Ask for one section and the walkthrough goes to that section. Ask for the whole document and it is taught in order, start to finish, and takes as long as that honestly takes.

What file types can I upload?

PNG, JPEG, WebP and GIF images, PDF, plain text and Markdown. Up to 5 files, each under 10 MB, and at most 20,000 characters are read out of any one PDF or text file.

What happens to the file I upload?

You can attach up to 5 files, each with your own one-line note. An image is resized in your browser and uploaded to storage only our build worker can read. A PDF or a text file is never uploaded - its text is read in your browser, and only that text travels with your request, where the model that plans your course reads it. The privacy policy sets out what is stored, who can see it and for how long.

How long will the video be?

You pick the runtime on the last step, and the build spends exactly that much of your monthly minutes. The content track opens at 15 minutes and the ladder runs to 30 hours, so a single chapter and a whole book are the same control set at two different rungs.

Is this the same as a summary of the document?

No. A summary shortens the document. A walkthrough teaches the part you need, at the level you already have, and names where in the document each point came from so you can check it against the page.

Is it legal advice if my document is a contract?

No. A walkthrough of a contract shows you what your document says at the clauses that matter and names them. It does not say whether to sign. We are not your lawyer and this is not legal advice.

Make a video
Make a video