How it works
Everything about using Imprintal: the web app, the terminal designer, Claude Code, getting files ready for a printer, and credits. Can’t find it? Write to support@a1base.com, or use Feedback in the app.
Getting started
Sign up with your email address. There is no password: we email you a 6-digit code (valid for 10 minutes, three tries) or, if you prefer, a sign-in link (valid once, for 10 minutes). Google sign-in appears when it is switched on. A session lasts 30 days.
Your account comes with a personal workspace that only you can see. The first time you sign in, a short setup lets you start a team workspace, try the sample document or upload your own, and connect the terminal or Claude Code. You can skip any step.
To protect your inbox, we send at most three codes or links a minute to one address. If one doesn’t arrive, check your spam folder, then wait a minute and ask again.
Trying it without an account
Try it designs one document as a magazine with no account. Drop a Markdown file and the pictures it uses (up to 300 KB of Markdown and 10 PNG or JPEG pictures, 8 MB in all), pass the quick bot check, and download the PDF after a few minutes, with its page count and whether every hard check passed.
A whole magazine issue works too, when it fits those limits: it comes back as an issue, with its cover, ads, contents and openers, shown as spreads and named by the genre look it was given. There is a sample issue to try.
A free try uses AI planning and visual review. Add an optional design brief for the style you want. The designer reviews page previews and can refine the layout, within the free trial’s limit. No new pictures are generated, and you need no credits. Your text is set exactly as written, and nothing is printed about how the pages were made. Each visitor gets 5 tries a day, and the service has a daily limit for everyone; when either is used up, the page says so and when it opens again (00:00 UTC). If the designer is busy, wait a moment and try again: a try that never started doesn’t count.
Your file and the magazine are deleted within 24 hours and used for nothing else. To keep a design, change it with the designer, or export it for print, sign up free and upload the document to a project.
The web app
Workspaces
Projects, credits and the plan belong to a workspace, not to a person. You always have your personal workspace, and you can create team workspaces from the switcher at the top left. Switch between them there; each has its own address, /app/<name>.
Projects
A project is one Markdown file and its images. Choose New project, then pick the file and its images, drop them, or drop the whole folder; or start from the sample. Only the images the document uses are sent, by the names it uses, and the text is never changed. The limits: the Markdown up to 2 MB, and up to 40 PNG or JPEG images, 20 MB each and 60 MB in all.
Then design: Design with AI opens the designer to plan, inspect and refine your document with you, using the same design tools as the terminal. House layout is the simpler offline option for a report and magazine, or for a magazine issue alone (it costs only its renders). Click a page to see it large, and lock the pages you approve; a later change that would move a locked page is refused. Export for screen, print or press: print and press need a print copy of a design (with bleed), and come with the preflight report on the page. Before anything that spends credits you see about how many it takes.
Every change is a revision with the name of the person who made it (or the designer for its rounds), and any revision can be restored: reverting adds a new revision, so nothing in the history is lost.
Share links
Editors can make a read-only link to one rendition of a project: anyone with it sees its pages and can download its PDF, without signing in. A link is shown once (we keep only a fingerprint of it), can expire after a day, a week, 30 or 90 days, and stops working at once when it is revoked or the project goes to the trash. Shared pages are never listed by search engines.
The trash
Editors can move a project to the trash: it leaves the list and its share links stop, but its files are kept and anyone who can edit can restore it from Trash for 30 days (its share links then work again). While it is in the trash nobody can change it, in the web app, the terminal designer or Claude Code, which don’t list it. After 30 days it is deleted for good. Admins and the owner can also delete a project in the trash at once.
Inviting people
Owners and admins invite people by email from Members, with a role. The invitation link is valid for 14 days; the person signs in with the address it was sent to (which must be verified) and accepts. On the Free plan a team workspace has 3 seats, and pending invitations count; cancelling one frees its seat.
Roles
| What | Owner | Admin | Editor | Viewer |
|---|---|---|---|---|
| View projects, pages and PDFs; open share links | ✓ | ✓ | ✓ | ✓ |
| Create, design, iterate, lock and export (spends credits) | ✓ | ✓ | ✓ | – |
| Make and revoke share links; move to the trash and restore | ✓ | ✓ | ✓ | – |
| Delete a project for good | ✓ | ✓ | – | – |
| Preview brand kits and apply them to projects | ✓ | ✓ | ✓ | – |
| Save and delete brand kits; set the default kit | ✓ | ✓ | – | – |
| Start research, answer it, edit and approve its draft | ✓ | ✓ | ✓ | – |
| Generate images, press exports | ✓ | ✓ | ✓ | – |
| Invite people, change roles, remove members | ✓ | ✓ | – | – |
| Rename the workspace | ✓ | ✓ | – | – |
| Transfer ownership, delete the workspace | ✓ | – | – | – |
Admins can’t change or remove other admins; only the owner grants or removes the admin role. Ownership moves only with Transfer ownership in Settings, which makes the old owner an admin.
Leaving and deleting
- Anyone but the owner can leave a team workspace from Settings.
- The owner deletes a team workspace by typing its name. Its projects go with it.
- You can delete your account from Account settings by typing your email, if you signed in within the last 24 hours. It deletes your personal workspace and any team workspace you are alone in. While you own a team with other members, transfer ownership first.
Feedback
Choose Send feedback in the account menu (your initial, top right) inside any workspace. Tell us what worked, what didn’t or what you need; it goes straight to the people building Imprintal.
Writing a magazine issue
A magazine issue (a cover, ads, a contents page, sections of articles, each with its opener) is one Markdown file, like any other document, written so the engine can read its parts. When it does, the project page says Recognised as a magazine issue and shows the issue’s structure beside its pages, with the pages each section, article and ad takes. The text is set exactly as written: nothing is rewritten, trimmed or reordered.
The grammar in brief
# Titleis the magazine’s name (its masthead). The paragraph right after it is the issue line, such as The Craft Issue · November 2026 · $14.99 US.- Optionally, a list of three to five cover lines, each with a bold lead, and a cover picture with an italic caption, before the first section.
## Sectionheadings in reading order (Notebook, Features…), and inside them### Articleand### Adheadings in print order;####for subheads.- Under an article’s heading: a dek (a paragraph wholly in italics), then a byline starting “By ”. Interview questions are paragraphs wholly in bold; a poem keeps its line breaks (end each line with a backslash).
- An ad is a
###heading with the brand as printed, exactly one picture under it, then up to about 90 words. Name every ad in the frontmatter underadvertisements:. Ads before the first section open the issue (the first is the inside front cover); the last one or two close it.
A document is read as an issue when its frontmatter names ads or has an issue: block (date, number, price), or when two or more of its articles carry a dek or a byline, at least one of them a byline such as “By Ana Ruiz” (or the issue line names the issue). If yours isn’t, add those. The full grammar, with examples.
Looks
An issue takes one of six genre looks, each its own faces, colours, columns and small styles: fashion monthly, literary journal, city magazine, premium trade quarterly, art journal, interiors magazine; or the house look. Choose it under Look on the project page, and the cover’s layout under Cover.
Articles and ads
Choose an article in the outline beside the pages to adjust it: its opener (headline, picture at the head, picture at the side, full-bleed picture, spread, type), one to three columns, whether it is ever quoted large in a pull quote, and whether it starts a new page or flows on after a short item. An ad’s page can be full bleed, framed, split, type; ads stay where you put them. Each change shows its cost first, can be previewed (a render that saves nothing), and is refused if it would move a page you locked, naming the page.
The engine fills pages as an art desk would (picture sizes, pull quotes, opener depth, columns) and says what it did as notes on each page, with advice where a page is still part-empty or type sits on a picture’s subject.
A stapled (saddle-stitched) issue needs a multiple of four pages; the engine adds pages before the back covers, the issue’s own pictures first, and says which. Make a print copy, then Export for print: the preflight report’s Binding line gives the count and whether it fits.
A project takes up to 40 pictures, 60 MB in all, with their progress shown as they upload; a free try takes up to 10.
Brand kits
A brand kit is a workspace’s look for reports, set once: a logo (SVG or PNG, with an optional light version for dark fields), six colours (paper, ink, two accents, a dark and a muted one), three faces from the bundled set, the report style and cover, a footer line printed on every page, a contact block and a back page. A workspace can hold several kits, for clients or sub-brands. Open Brand kits in the workspace.
The page checks the kit as you type, field by field: body ink must reach 7:1 against the paper and the muted colour 4.5:1; an accent too light for text is kept for rules and fields; an SVG with a script, an outside reference, live text, a filter or a mask is refused (convert text to outlines); a PNG too small to print sharply is refused. A sample (a cover, an inside page and the back page of a short fictional report) renders as you edit, after a pause; each sample is one render, 1 credit.
Editors preview kits and apply them on a project’s page; admins and the owner save and delete them and choose the default kit, which is offered when a research report is approved. A project keeps the version of the kit it was given: when the kit changes, the project says so, and applying it again is a new revision you can undo. In the terminal: pnpm designer brand, or /brand in a session.
Publishing a report
Editors can publish a rendition as a page of its own at /r/<workspace>/<address>: its title, the cover, a summary in the document’s own words (you pick the blocks; the executive summary or abstract is suggested), the first pages as pictures, your brand kit’s logo and colours, a web reading version, and the PDF. Open the project and choose Publish this report. Only a rendition whose current pages pass every check can be published, and you publish the revision you are looking at.
- Open: anyone can download the PDF. Gated: a short form first (the email address always; name, company, job title and country if you turn them on; one consent box and one question in your words). A gated page needs your privacy policy’s address; the form names you as the one receiving the details. Unlisted: only people with the link; search engines are asked not to list it.
- The address is random until you name it. Words such as
readordownloadare reserved. - After the form, the reader gets a download link that works for 30 minutes. Emailing the link too is off unless you turn it on: then one email in fixed words (nothing you wrote is in it) with a link that works for 72 hours, within daily limits per address and, for your workspace, per email domain, publication and in all (the reader’s answer on the page is the same whether it went or not). Nothing else is ever sent to them. The PDF of a gated page is never at an address anyone can guess.
- Unpublish takes the page down at once; its address, settings and leads stay. Publishing again makes a new version at the same address. A project in the trash takes its pages down; deleted for good, its publications are unpublished, and a new project with the same id never brings them back.
Leads
Leads (in the workspace) lists who filled in a form, with each consent box’s words and when it was ticked or left empty, for editors, admins and the owner; viewers don’t see it. Filter by publication or find an address, page through every lead, open one person to see all their leads and consents (however their address was spelled: ada+news@ is ada@), export them or delete them all (a request to be forgotten). See views, submissions, leads per view and downloads, export a CSV (the lead’s id first; cells that would start a spreadsheet formula are made safe), and delete a lead. Nothing confirms that an address belongs to whoever typed it, so a ticked box is not a verified opt-in, and a form sent again with an address you already have changes no field of its lead: what it typed is kept in the person’s view marked unverified. A later “no” to consent is always applied (a withdrawal is honoured even unverified); a later “yes” is not. Admins can delete all of a publication’s leads and choose how long leads are kept: 24 months unless you change it; older leads are deleted automatically.
Lead webhooks
Admins can send each new lead, and a later submission’s other consent answer (unverified), to an https address, so a CRM, Zapier or Make can take it: one hook for every publication and one per publication, in Leads. Private, local and metadata addresses are refused (a name that turns out to resolve to one fails at once and is not retried), a redirect is never followed, the receiver has 5 seconds to answer, and a delivery that fails is tried again after 10 and 30 minutes, 2, 6 and 24 hours. The workspaces that waited longest are served first. At most 100 deliveries wait per hook; the hook says how many were dropped, and Resend failed queues each failed lead again once (3 times an hour per hook). A hook whose last 15 attempts all failed is turned off until you turn it on again. Send test delivers a made-up lead now (10 an hour, one at a time). Each hook has its own signing secret, shown once.
The request is a POST of JSON:
{
"event": "lead.created", // or "lead.consent_changed", "webhook.test"
"verified": false, // nothing confirms an address
"id": "dlv_…", // the delivery, the same on every retry
"createdAt": "2026-11-19T12:00:00.000Z",
"workspace": { "id": "…", "slug": "northwind" },
"publication": { "id": "pub_…", "slug": "cold-chains-2026", "title": "…", "url": "https://…", "version": 2 },
"lead": { "id": "…", "email": "…", "name": null, "company": null, "jobTitle": null, "country": null,
"question": null, "answer": null, "consent": true, "consentText": "…", "consentAt": "…",
"createdAt": "…", "updatedAt": "…" },
"submission": { "consent": false, "consentText": "…", "at": "…", "verified": false } // lead.consent_changed only
}with the headers x-imprintal-event, x-imprintal-delivery, x-imprintal-timestamp (Unix seconds) and x-imprintal-signature: sha256= and the hex HMAC-SHA256 of the timestamp, a full stop and the raw body, keyed with the hook’s secret. Check it before trusting a delivery, and refuse an old timestamp. Answer with any 2xx status; a 4xx other than 408 or 429 stops the retries.
Research reports
New report on the projects page starts a researcher on a question. You give the audience, the length, the report’s shape (a market scan, a competitor review, a due-diligence memo, a strategy options paper or a policy brief), links you want used, files to read (PDF, Word, Excel, CSV, Markdown or text; up to 10 files) and your own notes. Before it starts you see its budget: at most 12 web searches, 30 page reads and 600,000 model tokens (counted as they are charged: what the researcher re-reads of its own conversation from the cache counts at a tenth, everything else in full), so up to 72 credits; a search costs 0.5 credits, a page read 0.2 credits, and the model what it reads and writes. You are charged what the run uses.
The researcher plans, reads, and shows you an outline to approve. Then it writes a draft where every figure and claim carries a footnote quoting the passage it rests on, and the page lists the checks by line: a footnote that names no source, a quote that is not in its source, an attribution that does not match, a source never read, and figures with no citation (advice). You can edit the draft yourself: your lines are kept, and later versions must carry them. The checks show that each quote is in its source; they do not show that the source is right.
Only an editor, signed in, approves a draft, with the Approve button after reading it; the researcher cannot, and no MCP client can. The approved draft becomes a project’s Markdown word for word, the default brand kit is offered, and the designer lays it out without changing a word. Where web search is off on this server the researcher works from your files, notes and links, and the page says so.
The researcher’s questions are answered by the person who started the run or by an admin; any editor may approve the draft, and the run records who did. A run an MCP client starts waits on its page until a signed-in editor reads its brief, links and notes and presses Start; nothing is fetched or spent before that. The person who started a run, or an admin, can Delete run, which removes its uploads, sources and drafts (a project made from it stays).
The terminal designer
A designer you talk to in your terminal. Run it in the folder that holds your Markdown and images. It needs Node.js 20.3 or later and nothing else:
npx -y --allow-remote=all https://publication-designer-site.a1base.workers.dev/designer-0.1.0-ge1ae9a6dfe71.tgz- The first time, it opens your browser to sign in with your Imprintal account, and remembers you on that computer.
- It works in a workspace you choose, and its work draws on that workspace’s credits.
- Results (PDFs, page images, preflight reports) are downloaded to
./designer-output/<project>/next to your files. - Type what you want in plain words.
/helplists the commands:/projects,/opento open a PDF,/cost,/resumefor an earlier session, and/exit. - When a new version is published it tells you, with the new line to run.
Claude Code
Add Imprintal to Claude Code once, from any terminal:
claude mcp add --transport http --scope user imprintal https://imprintal.com/mcpThen, in Claude Code, run /mcp, choose imprintal and sign in with your account in the browser. Ask for what you want (“use publication-designer to make a report from notes.md”). The tools act in your workspace and use its credits, exactly as the web app and the terminal designer do.
Print and press
There are three ways out: screen (an RGB PDF for reading), print (an RGB PDF with bleed and the marks you ask for) and press (the print PDF converted to CMYK PDF/X-4 for a named printing condition). Print and press exports come with a preflight report.
Bleed
Bleed is set per edge, 3 mm unless your printer says otherwise; spreads use inside and outside. Art that touches the trim runs through the bleed, and everything inside the trim stays exactly as designed. If pages are locked, the print version is made as a copy, so your approved screen pages don’t move.
Marks
Crop marks, bleed marks and a page-information line sit in the slug, outside the bleed. Registration marks and colour bars are for press files only. All marks are off unless you ask; many printers want none. You can have single pages, which printers impose themselves, or reader spreads for proofing.
Printing conditions
For a press file, the designer asks which printing condition your printer names. It never picks one for you.
| Condition | Profile | Paper and press | Ink limit |
|---|---|---|---|
| FOGRA39 | Coated FOGRA39 (ISO Coated v2) | Coated paper, sheet-fed offset; the common European default | 330% |
| FOGRA51 | PSO Coated v3 | Premium coated paper, sheet-fed offset | 300% |
| FOGRA52 | PSO Uncoated v3 | Wood-free uncoated paper, sheet-fed offset | 300% |
| GRACoL 2013 | CGATS 21-2, CRPC6 | Premium coated paper, US sheet-fed offset | 320% |
| SWOP 2013 | CGATS 21-2, CRPC5 | Coated publication paper, US web offset | 300% |
The condition’s ICC profile becomes the PDF’s output intent. Text stays text, vectors stay vectors and transparency stays live.
Black
Small near-black text is set in 100% black ink only (K-only) and overprints, so it can’t print with coloured fringes. Dark neutral greys become a tint of black. Large dark areas get the condition’s rich black. Coloured text and everything else go through the profile.
The preflight report
Every print and press export comes with a report, as Markdown and as a short PDF, headed PRINT READY or NOT READY. It lists the trim and bleed, the page boxes, the output intent, any RGB left, fonts (embedded, none Type 3), ink coverage against the condition’s limit, black text, white overprint and every image’s resolution at its printed size, plus warnings such as small or reversed type. Send it to your printer with the files.
Colour is converted by Ghostscript and the press checks are our own self-check against PDF/X-4. It is not a certified PDF/X validation, so your printer’s preflight has the final word.
Checks
Hard checks block an export: text that overflows its frame, a word of your document missing from the pages, a font that isn’t bundled and embedded, wrong page geometry, marks too close to the art, art that stops short of the bleed, and images under 150 ppi at their printed size. The designer can’t weaken a hard check to make its own design pass.
Soft checks are advice: a near-empty page, a heading stranded at the foot of a page, loose lines, low contrast over a picture, a figure far from where it is cited, small type, images under 250 ppi. Each comes with the option that may fix it.
Your text is never rewritten, shortened or shrunk to fit. If something can’t fit, you are told what and where.
Credits and limits
Each workspace gets 300 credits a month on the Free plan, and each person can spend about 100 a day, counted across all their workspaces by email address. Your email address must be verified before anything is spent (signing in with a code or a link verifies it).
| What | Credits | Notes |
|---|---|---|
| Model tokens | 1 per 10,000 | Planning, looking at pages and revising. Cache reads count at a tenth. |
| A render | 1 | Laying out and checking every page of one edition. |
| A generated image | 5 | Only when you say yes to one. The designer asks first. |
| A press export | 3 | The CMYK PDF/X-4 conversion, its checks and the preflight report. |
| A web search (research) | 0.5 | A research report shows the most it can use before it starts: up to 72 credits with web search, searches, page reads and model tokens together, and usually far less. |
| A web page read (research) | 0.2 | Each page the researcher fetches: a link you gave it or a search result. |
| Looking around | Free | Briefs, capabilities, project lists, page images and PDFs. |
A call that would go over the workspace’s month, your daily cap, or the service’s own daily limit for everyone (it keeps a free beta affordable) is refused before it starts, with a message saying which limit and when it renews. Every call reserves the most it could cost first and is settled from what was actually used, never more than it reserved (a design run with the model reserves at most 40 credits, and if it reaches that it stops and says what it finished); output is counted even when a reply is cut short. The workspace’s usage page shows credits left, who used what and each person’s cap.
To keep the service fair there are also rate limits on sign-in, invitations and changes; if you hit one, wait a minute. See Pricing.
Privacy basics
- Your documents, images, renders, generated images and exports are stored in your workspace on Cloudflare, visible only to its members (and to anyone you send a share link).
- To design, parts of your document and page images are sent to the model provider (Anthropic, through Cloudflare’s AI Gateway). Images are generated only when you say yes.
- Nothing about how a page was made is printed on it: no credits, colophons or AI labels.
- Deleting a workspace deletes its projects; deleting your account deletes your personal workspace.
The details are in the Privacy Policy and the Terms.