Wyldcards Help Center

Find a quick answer, learn the basics, or explore every tool. Search with a few words to narrow topics.

Use the Down Arrow to browse results, Enter to open one, or Esc to clear your search.

What would you like to do?

Start here

1. Create or open a stack. 2. Add a card for each idea, scene, song, or record. 3. Choose Edit to add fields, buttons, and widgets. Start with the Welcome overview, then see Edit Mode when you are ready to build.

🃏 Welcome to Wyldcards

Wyldcards is a HyperCard-style tool. You make a stack, fill it with cards, put fields, buttons and widgets on them, and write short scripts that say what happens when someone clicks. A screenplay, a songbook, a checklist and an ear-training drill are all just stacks. Across the app, solid buttons confirm or create, outlined buttons navigate or offer secondary actions, and red buttons remove something.

A card's toolbar keeps Find, New card and Edit in view. View holds the ways to look at a stack (List, Map, Scroll stack, Storyboard, Canvas, Outline, Navigator, Recent cards and more), and More holds the rest: Comments, Bookmark, Practice, Flip, Present, Message, Capture, Paint, Mark, Make public, Compare, Print and Export. The Edition menu beside the stack's name appears once a stack has more than one edition. View > List shows each card with its first few fields; a ticked check box reads as ✓ and its name (an unticked one is left out), and marked cards carry a Marked tag.

In Edit mode the edit bar is one row: + New card, the Add controls, the card's name, and five menus. Layout switches, copies or saves the card's layout as a template. Card holds Move to stack, Cards, Version history, Changes, Related cards, Presenter notes, Card date, Tags, Can't delete, Don't search, Archive card and Delete card. Part holds Copy, Cut, Paste, Select all parts, Arrange and Components; Scripts opens the card, background and stack scripts; Stack opens Data and Archived cards.

Header and toolbar menus work with a keyboard too: use Up and Down Arrow to move through options, Home or End for the first or last option, and Escape to close the menu and return to its button.

📐 Stacks, Backgrounds & Cards

Adapt cards for phones in Stack Settings makes cards flow top to bottom on screens up to 600px wide, using their original top-to-bottom, left-to-right positions as reading order. It applies to browsing, public shares, and published stacks. Desktop layouts and printed cards keep their original positions. In Edit mode, use Preview beside Selected part to check Phone, Tablet, or Desktop; previews are read-only. Choose Edit layout to resume arranging parts. Turn on the stack setting to see reflow in the Phone preview.

A stack is an ordered pile of cards. Every card sits on a background: parts placed on the background appear on every card that uses it, while parts placed on a card belong to that card alone. A background field keeps separate text per card unless you mark it shared.

In Edit mode, use Layout to apply another background to the current card or duplicate its current layout before changing it. Layouts are reusable forms for the same stack's cards. When you switch layouts, values in non-shared background fields with the same name carry over; other fields remain available when you switch back.

Browse with the arrow keys or with Prev / Next buttons of your own. The last card wraps round to the first.

In Browse or Present mode, choose More > Flip (or press F) to turn the current card over and show its stack and card label. Choose Front or press F again to return to its content. Flipping is temporary and never changes the card.

In Edit mode, choose Card > Presenter notes to write private notes for the current card. Notes never appear on the card, in print, or in public shares. When an editor presents the stack, choose Notes to read them without showing them to the audience.

A stack's Settings page opens with a list of its sections — name and icon, card size, design, history, sharing, protection, public links, automations and publishing — so you can jump straight to one; on a wide screen the list stays beside the form and marks the section you are reading. Open Settings to set the size of every card in the stack. Choose Classic, Widescreen, Square, or Portrait to fill in common dimensions, then adjust the width and height if you need a custom size.

Open Settings to choose a card design for the whole stack. The design presets apply in the editor, storyboard, shared links, and print view. You can also add supported CSS declarations to refine the background, border, text, or shadow; use declarations only, not selectors or external URLs.

In a stack's Settings, add an optional web link. A card's More menu then shows Open link, which opens that page in a new tab.

In Edit mode, choose Move cards, select another stack, then drag a card by its grip onto the other stack. You can also use Move left or Move right. The card keeps its content and recordings; its background is copied into the destination stack.

You can also type it in the Message Box: move card to stack "Songs" moves the card you are on to the end of the stack named Songs, and copy card to stack "Songs" puts a copy there instead. Say to the start of stack "Songs" to put it first, add and go to follow it, or use move marked cards to stack "Archive" to move every marked card in order. The stack is found by name, in any case, among the stacks you can edit.

Stack Windows

Choose More > Compare on a card, then tick up to three additional stacks. Each window is a complete independent workspace: move through its cards, use its tools, and edit when you have editor access. Use Open separately in a window's title bar to give it its own tab. Above each workspace is a strip of the stack's cards: choose one to open it in that window. To move a card to another stack, drag its tile into the other window and let go where it should go among that stack's cards, or anywhere on the workspace to put it at the end; the window opens at the card that arrived. Hold Option (Alt) as you let go to copy the card instead, leaving the original where it was. Drag a tile along its own strip to reorder the stack, press Esc to cancel a drag, and on a touch screen hold a tile before dragging it. A tile's button moves or copies the card to the end of another open window or duplicates it in place, and Alt + Left/Right Arrow on a focused tile moves it one place along. Cards move with their content, recordings, and a copy of their background, as with Move to stack; only stacks you can edit take part. On a narrow screen, the windows stack vertically. On a Mac or an iPad, the apps open stacks in windows of their own with Open in New Window and Compare With.

All Stacks

Signing in opens your Home stack; All stacks (the Stacks tab, or All stacks in the user menu and on the Home card) is where every stack is arranged. All stacks is a card in your Home stack, so it opens there with Home's buttons and menu around it. If your Home stack was made before it had that card, All stacks opens as its own page with a Put on Home button: press it to add the card to the end of your Home stack. If you archive or trash your Home stack, All stacks opens as its own page. New accounts start with an editable Start Here stack that introduces cards, parts, and layouts, with a QuickTips widget for extra guidance; change it, keep it as a reference, or delete it whenever you like. Press Arrange at the top of All stacks to give the page a name, switch between a list, a grid, or draggable columns, or choose the order (your own, by name, or most recent first). Columns scroll horizontally; with My order selected, drag a stack left or right to arrange it. The same order, dock first, is what the Home card's stack list shows. Under Widgets, add Quick Capture or the piano, metronome, beat builder, countdown, and sing widgets; they appear under your Home card, where you can drag them to rearrange. Quick Capture saves a card into the stack you choose; home instruments use their usual controls, but do not run card scripts.

Add to dock keeps a stack in the compact dock at the bottom of the page for quick access. In a custom-ordered grid, drag a stack onto the center of another stack to make a substack; drop at a tile edge to reorder instead. Archive and Trash stay visible in the dock: click Archive to browse archived stacks, or drag a stack you own onto Archive or Trash to archive it or move it to the trash. While dragging, drop on Dock Zone to add a stack there, drag a docked stack to Move out above the dock to remove it, or drag it directly onto the main grid to choose its new place; the dock scrollbar stays out of the way during the drag. A group tile shows the icons of its immediate substacks. Open a stack group to browse its substacks, create another substack, and repeat as deeply as needed. Every substack keeps its own cards and order. Use Move out on a substack to promote only it one level, or Ungroup to move all immediate substacks up one level. Under Start on, pick a stack to open instead of your Home stack when you sign in; Home stays one tap away.

Folders are yours alone: filing a stack moves it on your home screen and nobody else's, so you can file stacks shared with you too. Choose New folder at the top of All stacks, then drag a stack onto a folder tile (in a custom-ordered grid), or select stacks and choose a folder beside Move to folder. A filed stack leaves the top of the page (a docked one stays in the dock). Open a folder to see its stacks and the folders inside it; there you can move a stack to another folder or back to the top, add a stack, make a folder inside, rename the folder, move it into another folder, or delete it. Deleting a folder keeps everything in it: its stacks and folders move up to where it was, and a folder whose name is already taken there gets a number after it. Folders go up to 12 deep. Under Start on, pick a stack to open instead of the list when you sign in, the way HyperCard opened its Home stack; the list stays one tap away.

Use the Search box at the top of All stacks to find a stack by its name or description, or search the names and text of its cards and fields. It also finds your private presenter notes and the titles or filenames of audio attachments. Press / anywhere on All stacks to focus it.

Use Select stacks to choose stacks you own, then archive several at once or move them to the trash. Choose Done selecting to clear the selection. Open Archive or Trash from the user menu to browse stacks you put aside. Restore a trashed stack to bring it back, or delete it permanently. Shared stacks cannot be selected because only their owner can archive or delete them.

Bookmarks

In Browse mode, choose More > Bookmark on a card to save that card privately for later. Open Bookmarks from the user menu, or press Bookmarks on your Home card, to see saved cards from every stack you can open. Each saved-card row includes a short preview of its fields when available. Bookmarks are personal: other collaborators cannot see or change them, and removing a bookmark never changes the card.

🧩 Template Stacks

Choose Music Notes in the template gallery for three playable melodies: a C major scale, Twinkle, Twinkle, and a dotted-note dance. Clone the template, press Play melody, or edit the notes, tempo, and sound before playing. Choose triangle, sine, square, or sawtooth for the sound. Stop ends playback; Copy melody makes a new card for your own tune. Each card includes a notation guide.

Every new account starts with Introduction, an editable tour of cards, fields, buttons, backgrounds, and widgets. You can also clone it from the template gallery. Other ready-made stacks include a Screenplay (a project card, one card per scene written in screenplay styles, characters, cast, contacts, to-dos and songs), a songbook (a title page, a contents card, one card per song, and a setlist), Checklists (to-dos filed under lists and sections, each with a note, a due day, a flag and steps), Travel (a card per trip with its dates, budget, packing list and a countdown, and a card per flight, stay or plan linked to it), a Task Board, a Simple Form with name, email, subject, and message fields, and Solfège, a movable-do sequencer with ear training. Task Board gives every task a card with Task, Status, Assignee, Due date, Priority, Notes, and Done fields. Open Data to sort or filter tasks by those fields and save a private view such as "My work" or "Due this week." Clone Simple Form, tailor its questions, then choose Use first card as a public form in Stack Settings before sharing it to collect responses. Add a stack_view widget to any card for a compact, linked index of every card in that stack. In the Screenplay, the scenes read as one script: Read the script opens the page view with the title page first, and a song card put into a scene ([+]) is sung there in its current words. Each scene card shows how long it runs (“142 words · 0.6 pages” — a page is about a minute on screen), counted as you write; 🔊 Listen reads the scene aloud as a table read, headings and abbreviations said in full and notes left out, and a second click stops it; each character is read in the voice their card's Table read voice names — type part of a voice's name (🗣 Voices lists this device's, 🔊 tries one), and a voice this device lacks falls back to the default. Type = to start a Synopsis paragraph. The project card lists the scenes, numbered, by their headings, the characters, and every location with how many scenes happen there; pick one to go to its first scene. Each character card lists under Speaks in the scenes where that character has dialogue, with how many speeches, and totals the scenes, speeches and words; pick a scene to go to it. Typing a scene heading offers INT./EXT., then the locations already in the script, then a time of day. Each character's Played by links to an actor card, and each actor's Auditioned for to the characters they read, so either card shows the other. In Checklists, the front card gathers every to-do still open, flagged ones first, and says which are overdue; each list card shows its own, and + New to-do here files the new one under that list. In Travel, a trip card lists its own flights, stays and plans in the order they happen, by day and then time, counts down to the day you leave (“In 17 days”, then “Day 3 of 8”), and lists under Still to book the plans whose booked box is not ticked. Against its Budget it adds up what every plan costs as Planned and what the ticked ones cost as Booked; Left is the budget less what is planned. + Flight, + Stay and + Plan make a plan already linked to the trip; a plan counts down to its own day, and with an Until day — a check-out, or an overnight flight landing — says how many nights it is. A plan's Map ↗ finds its Place on Google Maps, and its day goes to Google Calendar. + New trip starts with a packing list to edit, and Untick all clears the ticks to pack again. The front card lists every trip by the day it starts and every plan in order. Picking a Due day sets the card's date, so Google Calendar sync sends it, and a to-do past its day shows Overdue until it is ticked done. Ticking the last step does not tick the to-do — that is your call. To take one off the list, archive the card in Edit mode; it can be restored. Reports in Data group the to-dos by List. In the Songbook, each song's words and the chords above them are one styled paragraphs field, in sections you name — Verse 1, Chorus, a note to the band. Click the Key control in a song header to choose the tonic and whether it is major or minor, or use its Transpose row to move a step at a time: the chart follows, every chord respelled the way the new key writes it (sharps in A, flats in E♭) and still sitting over the word it sat over. Under the song, Meter counts the syllables in each lyric line, part by part (Verse 1: 8-6-8-6 ABAB), and letters the lines that rhyme — X is a line that rhymes with no other in its part — along with the song's lines, words and syllables and its longest line. Syllables lists every lyric line split where its words divide (car·ry), each with its count. The counts and rhymes are read from spelling, like the Songbook app's, so take them as a guide. Read aloud says each lyric line in turn, pausing between parts (click it again to stop), and ▶ Play demo plays the song's first recording. To mark a lyric line the way the Songbook app highlights one, put the caret in it and choose Rework (yellow) or Keeper (green) in the style picker; choose Lyric to take the mark off. A marked line is still a lyric line to Meter, Syllables, Read aloud and Sprint, and the contents card counts the lines still to rework in songs that aren't archived. Tick Starred under a song's title and it heads the contents card with a ★. Tick Archived to take an old draft out of the book without deleting it: it moves to the Archived list at the foot of the contents card, still a click away, and the count above says how many there are. Type a Folder name beside those boxes to file the song, and the contents card lists every folder: click one to show only its songs (the count says which folder), and All songs to show them all again. Compare with… lines the song up against another one you name — a copy made with Copy song, say, or an old draft — and lists only the lines that differ: − for a line only in this song, + for one only in the other, with the summary on top (1 line only in “Porch Light” · 2 changed). Lines are matched by their words, so respacing a line is no change. Once you type in a song, the contents card also counts the days in a row you have written (✎ 3 days in a row), as the Songbook app does: any day you change a song's words counts, even a day spent cutting, and the count is kept in this browser. Tick A to Z on the contents card to list the songs by title rather than in book order; starred songs stay first. Sprint starts a writing sprint on the song: choose how many minutes, write, and the button counts down. When the time is up you are told how many words you wrote in the song's lyrics. Click Sprint again for the time left or to stop. The contents card lists the songs and not the title page, and Find in songs… searches every song's title and words; Print the book prints the whole stack, title page first. The solfege drill plays ascending and descending major and natural-minor scales, then lets you identify individual notes. Clone one, then change anything — the copy is yours.

In Solfège, each sequence is a card: press the syllables below the grid (or digits 1–8 for Do to Do', 0 for a rest, = for ~ Hold, which holds the note before it a beat longer) to fill the steps, add a scale or arpeggio from Add a pattern, and type the words into Lyrics, one per step. Do is the key you pick, so Play sounds the same tune in any key at the card's tempo, lighting each step as it sounds; turn on Loop, a Drone on Do, or Hide names to hear it without reading it. Lead-in plays Do Mi Sol Mi Do in the key before the first step, and A cappella lights the steps in time without sounding them, so you sing the line on your own. Hands shows the Kodály hand sign for the step being played or picked. 🎤 Sing back listens as you sing: the dashed step is the one to sing, the bar fills while you hold it in tune (and says a little higher or lower when you are not), and after about half a second held the step turns green and the next one comes up — tap a step to hear it and sing that one instead. 🎤 Karaoke plays the line and scores every step as it passes: green in tune, amber close, red off, struck through if you sat it out. Singing an octave lower still counts. Headphones keep the tune out of the microphone. 🎤 Record writes what you sing: hold a note for about a third of a second and it becomes a step at the picked step or the end, named in the card's key — take a breath between two of the same note. Random key plays each pass from a new Do without changing the card's key, and says which it was when you stop. The Sing widget beside it shows the note you are singing. Add a pattern has all twenty-eight of the Solfege app's scales, arpeggios and patterns. ⤓ WAV saves the sequence as a sound file. ⤓ MusicXML saves the sequence as a score — in its key and tempo, held notes tied across bar lines, the lyrics under the notes — to open in MuseScore, Finale, Sibelius or Dorico; ⤒ Import reads an uncompressed MusicXML score back in, naming its first part's notes from the key signature's Do and rounding anything shorter than a beat to one.

The Solfège Ear training card drills Scale degrees (a cadence sets Do, then name the note — or sing it into the tuner below), Intervals, Chords (major, minor, diminished, augmented), Scales, melodic Contours and Dictation, where you write the syllables you heard. Choose Easy, Medium or Hard; each question starts from a new Do. A wrong answer says what it was and why — how many semitones off, a song that opens with that interval, what sets one chord or scale apart from the other. Press 1–4 to answer, R to hear it again and N for the next. It counts your score, streak and best streak, and asks the names you miss more often; that record stays in this browser. 📊 Progress shows each drill's accuracy, its best streak and the answers you miss most; Start over forgets them. The Hand signs card pictures and describes the Kodály hand sign for each degree, with a scale to play, sign along with, or sing back.

In Recipes, tick ingredients off as you cook and start the kitchen timer from a recipe card. Scale... adjusts measured quantities for the number served while leaving instructions such as “salt to taste” unchanged. + Plan a meal puts a recipe on a day; set the meal's Serves to scale it. On the Shopping list card, choose a date range and Build from meals to combine the scaled ingredients into a checklist.

You can look through any template before you clone it — or before you have an account. Choose Preview on a template in the gallery, or open /templates without signing in, and step through its cards with the arrows. Scripts don't run in a preview and nothing can be typed, so buttons that move between cards by script stay still; Clone this stack (or Create an account to use it) makes a copy you can use.

While editing a stack, choose Contact from + New card to add a blank contact card with fields for name, company, role, phone, email, address, and notes. It uses the current background and fits the stack's card size. Open Templates in the card controls to save the current card's layout with a name. Saved card templates are available from + New card anywhere in that stack. They copy the selected background, parts, and styling into a blank card; they never copy the card's title, field text, scripts, notes, or mark. Delete a saved template from the same Templates menu when it is no longer useful.

In Edit mode, use Card name in the card controls to name the current card. The name saves as you type and appears in card navigation, search, and card links. Leave it blank when a numbered, untitled card is enough.

In Edit mode, choose Archive card to take the current card out of normal navigation without deleting it. The card archive opens after it is filed, where an editor can restore it at any time. Only people who can edit the stack see its archived cards. A stack always keeps one active card, so its last active card cannot be archived.

📦 Export & Import

Use More > Export in Browse mode or Download stack backup in Settings to export a single .wyldcards.json file holding its backgrounds, cards, parts, scripts, presenter notes and field text, and its script title page. Links between the stack's own cards — a linked cards field, or a song put into a scene — come back pointing at the imported copies, not the originals; links to cards in other stacks are kept as they are. Import it into another account, or keep it as a backup. Because a backup carries scripts and private notes, only the owner and editors can download it or the Markdown copy; viewers and writers cannot. Download Markdown creates a portable .md copy of card titles and field text; it does not include layouts, widgets, or scripts. The iPhone, iPad and Mac apps download Markdown and import all three kinds of file, with the same preview. Markdown imports as editable plain text: # names the stack, ## starts a card, and ### starts a field. To import, drop the file anywhere on the Import page or on All stacks, or choose it on the Import page: the preview opens straight away. You can also drop a folder containing exactly one .wyldcards.json, .md, or .docx file; drop one file at a time, since each becomes its own stack. In a Word document, Heading 1–9 styles name new cards; ordinary paragraphs and table text become editable card text. Long sections break between paragraphs where possible and continuation cards are numbered. Word imports size their cards to fit the imported text. Wyldcards validates and previews its stack name, cards, backgrounds, and parts before you choose Create stack; nothing is created until you confirm. On the preview you can rename the stack, file it in one of your folders, and choose what happens next: edit the first card (the default), browse it, open the stack's settings, or go back to All stacks.

Sharing a stack: its owner can use Share on a card to copy an existing public link, see who has access, and invite an active Wyldcards user by the email address on their account. Choose Manage sharing and passwords, or open Settings, to grant access by username or change and remove collaborators. An email invitation gives access immediately and includes a link to the stack. A viewer can browse and search the stack; a writer can also type into fields (and undo, redo and put back changes) but not change cards or the layout; an editor can edit cards, fields, and layout. For anything in between, see Roles below. Anyone who can open a card can use Comments to discuss it; comments stay inside the stack's right sidebar and are never shown on public or published links. The comments panel is collapsed until you open it, and More → Comments in the card toolbar shows or hides it; while you browse a card nobody has commented on, the panel stays out of the way so the card gets the full width. When it is open, use Close to collapse it. New comments appear automatically while the card is open, without replacing a draft you are writing. Type @username to email that stack participant a link to the card; unknown names, people without access, and yourself are not notified. Authors can delete their own comments, and the owner can moderate every comment. Collaborators see their current Shared role in the card toolbar. Collaborators can choose Leave stack from the card toolbar to remove their own access. Only the owner can change sharing, settings, or archive and delete the stack. An email invitation to someone without a Wyldcards account sends them a link, good for 14 days, to make an account and join; the owner can withdraw it from Settings while it waits. Only the owner can change scripts. On a shared stack a script runs only after the owner approves it, and each collaborator chooses whether to run the owner's scripts — see Scripts on shared stacks.

Roles narrow viewer or writer access for a group of people — a cast who shouldn't see the casting cards, a writers' room that can read the budget but not change it. The owner opens Make a role under Collaborators in Settings (or /stack/…/roles), names the role, chooses whether it rests on viewer or writer access, and chooses what it does: Hide cards on a background leaves every card on that background out; a field set to Hidden isn't drawn, found or listed; Read-only shows a field but refuses typing (for roles resting on writer access). Rules go by name, so one rule covers a field on every background and every edition that has one of that name; renaming a field, or copying a background, keeps what each role did with it. Give the role to people, invitations or teams from the same menus as viewer, writer and editor; a change to a role applies the next time its people open a card. For people with a role that hides something, the card count, going next and back, Find, the storyboard, outline and canvas, printing, the page view and its Fountain and Final Draft files, card links and the change history all leave out what it hides. Pages that show a stack whole and can't leave things out — the card list, the map, reports, backups and exports, the API, and the data scripts read — are closed to them. Someone in two teams sharing the same stack gets the broader access: more access first, then no role over a role. A role that is still given to someone can't be deleted, so nobody ends up seeing more than it let them.

Editions are parallel copies of a stack — a script's blue draft beside its white one, a cut for the table read. The stack's owner chooses More > Editions… on a card, or New or manage editions… from the Edition menu beside the stack's name once there is more than one (or opens /stack/…/editions) to make one from the edition they are in: it copies every card and field, so changes to it don't touch the others (images, recordings, tags and links between its cards are not copied). Everyone the stack is shared with, directly or through a team, can reach every edition, and anyone who can edit switches between them from the Edition menu; only the original is listed among your stacks. Make default picks the edition people with edit access open. Publish to viewers picks the one people with view-only access see — they see no other, and when nothing is published they see the default. Editions can be renamed and deleted; the original stays. Sharing a stack puts every edition's scripts under review, and choosing to run a stack's scripts covers its editions.

Editing together. On a shared stack, an open card hears the moment someone else saves a change to it (or checks every few seconds if that connection is down). If you are not in the middle of an edit, the card refreshes with their change; if you are, a notice offers Reload for when you are ready, so nothing you are typing is swept away. Every save also says which version of the field you were editing: if someone else saved that field in between, your change is held back and a notice asks whether to Keep mine (save your version over theirs) or Load theirs (reload the card with their version). The iPhone, iPad, and Mac apps do the same: an open card shows changes saved on the web or another device straight away (a field you are typing into keeps your text), and a save made against a change you hadn't seen asks whether to Keep Mine or Use Theirs. Scripts and automations always save; an API client can opt in to the same check.

Teams, in the account menu, are groups of people who share stacks together — a production's cast and crew, a band, a class. Make a team and you manage it: add people by username, or by email (someone whose email belongs to an account is added straight away; anyone else gets an invitation link that lets them make an account and join), make someone else a manager, remove people, rename or delete the team. Everyone can see who is in their teams and the stacks shared with them, and can leave. A stack's owner shares it with a team they belong to from the stack's Settings, as viewer, writer or editor, or one of the stack's roles: everyone in the team gets it, people who join later get it, and people who leave lose it. Access that comes through a team shows as "through the team" under People with access and is changed on the team, not per person; access given to someone directly stays theirs even if a team share ends, and someone in two teams that share a stack gets the better of the two roles. Help in the account menu searches every Help Center topic by name, a related word or its text — best matches first, close spellings too — shows the topics you opened most recently before you type, and reads each topic in the app with a link to it in the Help Center. API Tokens… in the account menu lists the tokens that connect Zapier, n8n, or your own scripts, with when each was made and last used, and the webhooks those tools subscribed: Revoke a token or Remove a webhook there. The app's own sign-in isn't one of them, so revoking can't sign you out. Tokens are created on the web, signed in with your password or a passkey — the server won't mint a token for another token's session.

Settings can also add a password for signed-in collaborators, create a password-protected public link, or publish a stack at a permanent public URL. Cards are private by default: editors use More > Make public on a card to open its public settings, explain where the card will appear, and include it in public links and published stacks. Choose Public to remove it again. Public views only navigate among public cards. Share copies only the link, so send its password separately. Published stacks are read-only, script-free, and visible to anyone with the URL; unpublish them any time. Published URLs can be embedded on another website with an iframe; password-protected public links and the editor cannot be embedded. A public link can be read-only, or use its first public card as a form: each submission makes a new card in the stack. Form submissions collect unlocked text, number, multiline, rich-text, and checkbox fields; scripts, shared fields, links, lists, and widgets remain unavailable. In Stack Settings, customize the form's submit label and confirmation message. Add an HTTPS submission webhook to send a signed public_form.submitted event to an automation tool after a response is saved. The Automations section can add several webhook rules: each is triggered by a saved form response, can run for every response or only when a selected field equals a value or is not empty, and can be disabled without deleting it. Rules send the same signed event after commit, with an automation-name header. Webhook URLs must be public HTTPS addresses: Settings refuses loopback, private-network, link-local, and cloud-metadata addresses, checks again before each delivery, and does not follow redirects. A hidden bot trap and a five-submission-per-15-minute limit for each form and visitor silently ignore automated bursts without making visitors solve a challenge. The owner can revoke the link or stop submissions at any time.

Data tools

While editing, open Stack > Data from the edit bar or card list to work across the whole stack. Find and replace changes exact text in card names and field text; it asks for confirmation before making the stack-wide change. Filter finds cards whose named non-shared background field contains a value. Save a filter with a name to rerun it later; saved finds are private to you, even in a shared stack. Select Open table view to lay out those fields as an Airtable-style grid: choose fields, filter and sort the displayed records without changing the stack's own card order, rename records or edit cells in place, and add a blank record. In the grid, press Enter to save the current cell and move down its column, or Shift + Enter to move up. Add Tags from a card's Edit controls, then filter the grid by a tag. Save the current columns, field filter, tag, and sort order as a private smart view to reopen it later. Export selected non-shared background fields as UTF-8 CSV for Excel and other spreadsheet apps; formula-like values are exported as text and return unchanged when imported. CSV import first previews columns so you can map each one, choose a unique background field, then upsert: matching cards update and new keys create cards. Blank keys and invalid rows are reported. You can also mark, unmark, or delete marked cards; one card is always kept.

Use Card > Card date in the edit bar to associate one optional calendar date with a card. The Cards panel shows assigned dates. Card dates copy with the card and are included in stack backups. A script can set one with wyldcards.setDate, which is how the Checklists template's Due field and a Travel plan's Day reach the calendar. When the owner connects Google Calendar in Stack Settings, Sync now sends dated cards to the owner's primary calendar as all-day events. Changes to dates or titles on events created by Wyldcards return to their linked cards; unrelated Google events are never imported. Disconnecting removes Wyldcards' access but does not delete calendar events.

In a field's inspector, choose its style: text, rich text, number, date, time, email, link, checkbox, list, checklist, or dropdown. Mark a field Required to reject blank values. A non-shared background field can also be Unique across cards, so no two records in that stack can use the same value. These rules are enforced for browser edits, imports, and API writes.

A Linked cards field links as many cards as you like, from any stack you can open — a scene's cast from a Characters stack, a production's crew from Contacts. Type in its box to find a card by name (/ and Enter to link it) and choose × on a chip to unlink one; a chip opens its card. In the inspector, Link cards from keeps the search to one stack. Every linked card lists the cards that link to it under Linked from, grouped by stack and field, so a character's card shows every scene it is in. You see a linked card's name only if you can open its stack; otherwise the chip says it is a card you can't open, and a card that links from a stack you can't open is left out of Linked from. The iPhone, iPad and Mac apps link, unlink and open linked cards and show Linked from too. The field stores the linked cards' ids, one per line, which is what CSV export, the API and field(name) see; links do not travel in an exported stack.

A Styled paragraphs field holds text made of paragraphs, each drawn in one of the styles the field defines — a screenplay's scene headings, characters and dialogue, a song's sections and lyrics, meeting notes' headings and action items. Choose it as the field's Style, then pick a preset (Screenplay, Stage play, Song, Interview or podcast, Meeting notes, Outline) or write your own styles, one per line: character: Character | caps | indent 20 | enter dialogue | starts @ | suggest. A style can be default, caps, bold, italic or underline; align it center or right; indent and right set its margins in characters and space the blank lines above it; enter names the style Return starts next and tab the one Tab switches to; starts lists opening words (or a symbol such as @) that switch a paragraph to it as you type, and ends closing words (such as TO:) that switch it when you press Return; parens draws it in brackets; suggest offers the style's earlier paragraphs from this field on every card — and on a scene heading, a step at a time, INT. or EXT., then the script's locations, then after - a time of day (DAY, NIGHT, CONTINUOUS and the script's own); keep with next keeps it off the foot of a page, unbreakable keeps it whole on one page, and continued character ends a page that breaks inside it with (MORE) and starts the next by repeating the last Character paragraph with (CONT'D). highlight yellow (or green, blue, red or gray) draws the style's paragraphs under a marker pen, a line to come back to; printed pages and downloaded files leave the highlight off. as dialogue says which screenplay element the style is in Fountain and Final Draft files (scene, action, character, parenthetical, dialogue, transition, shot, lyrics, centered, section, synopsis or note); a style without it is the element its key names, and action otherwise. The picker above the text shows and changes the current paragraph's style. The field stores one paragraph per line with its style in front, like [scene] INT. KITCHEN - NIGHT, so search, CSV, the API and scripts all see plain text; outlines, prints and search results show the words alone.

Insert song…, in a styled paragraphs field's paragraph bar, puts another card's paragraphs into this field by reference — a song from your songbook into the scene where it's sung. Find the card by name (in any stack you can open), and it goes in after the paragraph you were in, drawn as a marked block under “♪ From” the song's name. It isn't a copy: the block shows the song as it reads now, so a change to the song shows in every script it was put into, on the card, in Pages, in the PDF and in every file downloaded from there. It takes the lyrics only (each line in this field's lyrics style, a blank line between sections), or everything with Everything, not only the lyrics ticked. Edit the song on its own card — click its name — rather than in the block; to take it out, press Backspace (or Delete) beside it once to mark it and again to remove it. A song shows only while the owner of the stack it was put into can open it; otherwise the block says it isn't available and pages and files leave it out.

Versions, in the same bar, keeps named versions of the field — a song's demo, its radio edit, the arrangement for act two. The field on the card is always the version being worked on: Save version keeps it under a name, Open puts a saved version back into the field (keeping what was there as a version first), and Publish chooses the version that every place the song is inserted shows, so a new draft stays out of the scripts until it's ready; with nothing published they show the field as it stands. The Versions page also lists every field the song is inserted into that you can open.

Focus, in a card's View menu (or F, Ctrl+Alt+F on Windows), puts the card's styled paragraphs field — the one you last typed in — alone on the screen: everything else steps back, the text sits in one comfortable column, the paragraph you are writing stays bright while the rest dim, and the page keeps it near the middle of the window as you type, like a typewriter. The bar at the foot counts the words on the card and how many this sitting has added (or taken away); its paragraph bar fades until you point at it. Esc, Leave focus or the shortcut again leaves. Focus is remembered in this browser, so going to the next card stays in it.

Read, in a card's View menu and in the Pages toolbar, opens the whole script on one quiet, read-only page: every card's styled paragraphs field in order, with its title page at the top and songs inserted by reference filled in, and no pages — the text reflows to the screen, and on a phone the indents narrow so dialogue still fits. Scenes lists every scene heading to jump to; A− and A+ change the text size, and you can choose a typewriter or book typeface and a light, sepia or dark page, all remembered in this browser. It is a plain article, so Safari Reader and other reading modes take it as it is, and Print prints just the script.

Spelling, a box in a styled paragraphs field's paragraph bar, marks misspellings with a wavy red line using an English dictionary that also knows your script: every word of its character names and scene headings, the screenplay words INT., EXT., V.O., POV and the like, and the words people have added to the stack. Added words can use any writing system and hyphens. Click a marked word for suggestions, Add … to this stack's words (for anyone who can type in the stack; everyone writing in it and its editions then has it), or Ignore here for now. Untick the box to go back to the browser's own spelling; the choice is remembered in this browser. It needs a current browser (Chrome, Edge, Safari 17.2 or Firefox 140 or later); older ones keep their own spelling.

Stats, in the Pages toolbar, counts the field: pages and screen time (a page is about a minute), scenes with their lengths in eighths of a page and the page each starts on, interior and exterior, day and night, how many words are spoken and how many are action, who speaks — speeches, words, scenes and their share of the dialogue, with extensions like (V.O.) folded into the name — and where it happens, with each location's scenes and pages. It counts by what each style is, so an interview's speakers and a stage play's lines count the same way.

Find and replace, in the same toolbar, works across every card (or the marked ones) in the styles you tick — by default all but the character cues, so renaming someone in the action and dialogue leaves the names above their lines alone until you tick those too. Find lists every place with the words around it before anything changes; Replace all then changes the cards you may type into, each as one change in Changes that you can put back. Words are found as typed, optionally as whole words and in the same case, and Keep capitals gives the replacement the found word's capitals. Songs inserted by reference are left alone.

Pages, in a card's View menu, sets out the styled paragraphs field from every card, in card order, as real-size pages in 12-point lines: a script kept one scene per card reads as one script. Choose US Letter or A4, standard, narrow or wide margins, where page numbers go (page 1 goes unnumbered unless you ask), a new page for each card, whether to start with the title page, marked cards only, and the zoom; the settings are remembered in this browser. Pages break the way the styles say — a scene heading or character never ends a page, dialogue splits with (MORE) and (CONT'D) — and Print prints exactly those pages. Download… offers the field as files. PDF downloads the script as a PDF made by Wyldcards, laid out by the same rules with the settings you chose and set in Courier on an exact typewriter grid (so a line that just fits can break a word differently from the screen) (a character Courier can't show, such as Japanese or emoji, prints as a question mark); print from your browser instead for another font or alphabet. Double-click a paragraph to open its card. With more than one styled paragraphs field, pick which one to lay out.

Title page…, in the Pages toolbar for anyone who can edit the stack, sets the script's title page: the title, a credit such as Written by, the authors, a source such as Based on the novel by…, the draft date, contact details and notes such as a copyright or registration. The title, credit and authors sit centred a third of the way down, the contact at the foot on the left, and the draft date and notes at the foot on the right. The title page comes before page 1, unnumbered and not counted, on screen, in print and in the PDF (turn off Title page to leave it out). With no title page saved, the stack's name is the title. Each edition keeps its own title page, starting as a copy of the one it was made from, so a blue draft can carry its own date.

The rest of Download… writes the field — every card's, or the marked cards' — with its title page: Word (.docx), where each of the field's styles is a Word paragraph style of the same name with its indents, spacing and keep-together options, on the paper, margins and page numbers set in the toolbar (Word breaks the pages itself, so there is no (MORE) or (CONT'D)); Plain text (.txt), typed out as it prints with a page-break character between pages; EPUB for e-readers, one chapter per card named for the card; Fountain, the plain-text screenplay format; Final Draft (.fdx) for Final Draft, WriterDuet, Highland and most screenwriting apps; and MusicXML, the field's lyrics as a score to open in MuseScore, Finale, Sibelius or Dorico — a quarter note for each word under one staff, with section names above it, ready to be set to music (only paragraphs in a lyrics style go in). Import… reads a Fountain (.fountain, .txt), Final Draft (.fdx), PDF, Word (.docx), EPUB or MusicXML (.musicxml, .mxl, .xml) file into the field — by what the file holds, whatever it is named: either onto a new card for each scene after the last card (filling the last card first if its field is empty, and naming each card for its scene heading), which needs edit access, or onto the card you came from, replacing its text. Each element lands in the field's style for it, so a song or interview field can take a screenplay too. A PDF script is read by where each line starts on the page — dialogue, parentheticals, character names and transitions at their usual indents — with page numbers dropped and a speech broken by (MORE) and (CONT'D) joined back up; a scanned PDF holds pictures of pages rather than text and can't be read. A Word paragraph keeps a style named for a screenplay element, or for one of the field's styles (so Wyldcards' own Word and EPUB files come back exactly), and is otherwise read by its indent; save old .doc files as .docx first. A score's first part is read for its lyrics: syllables joined into words, lines ending where the score marks them, and words above the staff as sections. Title pages (every part of a Fountain one; a Final Draft, Word or PDF one by where its lines sit) become the stack's title page when a whole script is imported onto new cards and the stack has none yet; notes, sections, lyrics and centered text are read; boneyard text, scene numbers and page breaks are left out; Final Draft dual dialogue comes in as one speech after the other.

A Calculation field is read-only and works out a number from other fields. Write field names in square brackets, such as [Quantity] * [Price]; addition, subtraction, multiplication, division and parentheses are available. Blank or non-numeric values count as zero, a ticked checkbox counts as 1 (so if([Booked], [Cost], 0) is the cost only once it is booked), and a formula that can't be read is refused as you save it, with what is wrong.

A formula can also reach past its own card. Name a set of cards — linked[Cast] for the cards linked in this card's Cast field, linking[Cast] for the cards whose Cast field links to this one, cards for the stack's cards or cards[Scene] for those on one background — and add it up with sum(linked[Cast], [Fee]), average(cards[Scene], [Pages]), min, max, or count it with count(linked[Cast]). round(x) and round(x, 2), abs(x) and if([Pages] > 2, 1, 0) (with <, >, <=, >=, = and <>) round off the set. A calculation on another card is worked out too, so totals can build on totals.

A formula adds up only what the person reading it may see: a linked card in a stack they can't open, or a card or field their role hides, is left out, so the same total can read differently for different people. One formula reads up to 300 cards, and the result is worked out as the card is drawn rather than stored, so it is not in CSV exports, backups or what scripts read.

Email Cards

In a stack's Card list while editing, tick one or more cards, enter a recipient address, and choose Email selected. The email includes each selected card's title and non-blank text fields in card order; it does not include layouts, widgets, scripts, recordings, or attachments. Only editors can send cards, and archived cards are not available from the list. The iPhone, iPad and Mac apps send cards too, from Email Cards….

Automation tools and API

Connect Zapier, n8n, Make, Pipedream, Power Automate, or your own script without sharing your password. Choose API tokens in the account menu, create a token named after the tool, and copy it; it is shown only once. Paste it into the tool with your site URL. Give each tool its own token and revoke it when you stop using that tool.

In Zapier, the Wyldcards app has instant triggers for new, updated, and deleted cards and new form submissions, actions to create, update, or delete a card with each field as its own input, and a Find Card search. Its update action and the n8n n8n-nodes-wyldcards community node can also mark or unmark a card. n8n includes a Wyldcards Trigger. Turning a workflow on registers a webhook for its stack, and turning it off removes it; the API tokens page lists every connected webhook and lets you remove one. A webhook stops sending once its owner can no longer open the whole stack — for example after they are removed, a stack password is added, or a role hides part of it. New cards are sent a few seconds after they're created, so they arrive with their fields filled in, and a burst of edits arrives as one update.

For other tools, send Authorization: Bearer <token> to /api with Accept: application/hal+json. One request to /api/stacks/{uid}/cards can create a card with its name and field values; every value is validated before the card is created. Stack, card and part scripts appear in API responses only for people who can edit the stack. Read the automation API guide for setup, webhooks, signatures, and examples.

iPhone, iPad & Mac apps

The native Wyldcards app for iPhone, iPad, and Mac signs in to your Wyldcards site with your username and password, then stays signed in with a session key of its own, so your password is not stored on the device. Sign In with a Passkey uses a passkey instead of a password — Face ID, Touch ID, iCloud Keychain, or a passkey on a nearby phone — and signs in to the same kind of session. To add one, choose your account name in the toolbar and then Add a Passkey…; it's named after the device and appears in your account's passkeys on the web too. Passkeys work with the app when your server is wyld.cards. Sign Out ends that session on the server, and resetting your password signs the app out. On the sign-in screen, Forgot Password? emails a reset link: paste the link from the email into the app to choose a new password. Create Account makes a new account on that server straight away, with a generated username and password and a starter stack; save the password when the app shows it, because it is shown only once. Stacks are listed in the same order as your home screen, with pinned stacks first; touch and hold (or right-click) a stack to Pin to Top, Unpin, Export Stack… as a .wyldcards.json file, archive it, or move it to the trash. Import Stack in the Stacks toolbar reads a .wyldcards.json backup, a Markdown .md copy, or a Word .docx document, as the web's Import page does, and shows how many cards, backgrounds and parts it will make; nothing is created until you choose Create Stack. Download Markdown… beside Export Stack saves a portable .md copy of card titles and field text, without layouts, widgets or scripts. Grouped stacks appear inside their folder stack; use Move Into or Move Out of Group from the same menu to rearrange them. Customize Home sets the list's title, how stacks are sorted, and which stack opens when you sign in. Capture adds a card to the end of any stack with a title and a note, then opens it. Capture also reaches you outside the app: on iPhone and iPad, choose Wyldcards in the share sheet to keep shared text or a link as a note that opens in Capture the next time you open the app; add the Quick Capture widget to the Home Screen or Lock Screen; or use the Capture a Note and Open a Stack actions in Shortcuts and Siri (Capture a Note adds the card without opening the app). Stacks and the cards you've opened show up in Spotlight search, and choosing one opens it in the app; signing out removes them. wyldcards://capture?title=…&note=… and wyldcards://stack/UID/card/ID links open the same way. Trash lists stacks you moved to the trash: restore one, delete one permanently, or empty the trash. Bookmarks lists the cards you bookmarked in any of your stacks; choose one to open it. Stacks other people shared with you appear under Shared with Me: as a viewer you can read them, as an editor you can also change cards, and scripts stay off while a stack is shared. Touch and hold a shared stack to Leave Stack…. On your own stacks, Sharing… shares the stack with another Wyldcards user by username, or by the email on their account to send an invitation, and lets you change someone's access or remove it. The same sheet creates a password-protected Public Link (optionally accepting form submissions), revokes it, and Publishes the stack at a public URL; only cards you choose Make Public for appear in either. On a card, Tags… adds it to the stack's tags or a new one, and the Storyboard's Show menu filters by marked cards or by tag. A styled paragraphs field — a screenplay, a stage play, song lyrics — is written a paragraph at a time: tap a paragraph to write in it, and the rest stay set out in their styles. Return starts the next paragraph in the style that follows (a scene heading is followed by action, a character by dialogue), typing a style's prefix into an empty paragraph changes it — INT. for a scene heading, @ for a character — and the style name beside the paragraph changes it or deletes the paragraph. Songs inserted by reference show where they sit and are edited on the web. Focus (Cmd + Option + F) puts the card's paragraphs field alone on the screen in one column: the paragraph you're writing stays bright while the rest dim, it stays near the middle as you write, and the bar counts the card's words and how many this sitting has added. The arrows in the bar move to the previous or next card without leaving focus. Editions in the card toolbar lists a stack's editions — parallel copies such as a blue draft beside the white one — for anyone who can edit it, and Open switches to another; the stack's name shows which edition is open. The stack's owner also makes a New Edition from the one that is open (every card and field is copied, so changes to it don't touch the others), and from an edition's menu renames it, makes it the default people with edit access open, publishes it as the one people with view-only access see, or moves it to the trash. The original can't be moved to the trash this way. Read in the card toolbar opens a stack with a styled paragraphs field as one quiet, read-only script, like the web's read view: the title page at the top, then every card's paragraphs set out in their styles, reflowing to the window with narrower indents on a phone. Its Script Files button saves the script as a PDF, Fountain, Final Draft, Word, plain text, EPUB or MusicXML file with the page view's settings (paper, margins, page numbers, a new page for each card, the title page), reads a Fountain or Final Draft file back in as a new card for each scene or onto one card, and, for editors, edits the title page. Scenes jumps to a scene heading; the text-size buttons, a typewriter or book typeface, and a light, sepia or dark page are remembered on the device, and the Page menu also reads only the marked cards or another paragraphs field. Outline in the card toolbar lists every card as a numbered heading with its field text beneath; people who can edit the stack rename cards and change text fields in place (other field types are marked and edited on their card), Titles Only hides the text, and the arrow beside a heading opens that card. Editors also move a card from its heading: up, down, to the start, or to the end, and the new order is saved for everyone. Paint opens the card's paint layer, the picture behind its parts: draw with a finger, an Apple Pencil, or the mouse, pick a color and a brush width, switch to the Eraser to take paint away, and Undo the last stroke. Choose This Card or Background — a background's picture shows on every card that uses it — and Wipe clears the one you are on. Save sends the whole picture, the same thing the web's paint mode posts, so a card painted on a phone looks the same on the web. Painting needs Authoring. Message Box is the apps' command line, like the web's: type a command, press Return, and it runs against the stack you have open. It understands go next, go to card 3, go to card "Name", find "text", put 5 into field "count", get field "count", sort by name, sort by field "Key" descending, mark all, unmark all, mark cards where "Key" is "C", new card, the number of cards, the name, the parts, and say "hello"; History brings back what you typed before, and help lists the lot. Commands that need the browser — visual effects, beep, play, and scripts written in _hyperscript — say so and stay on the web. Print Cards puts the stack on paper the way the web print sheet does: one, two, or four cards to a page, each card's fields where they sit on the card. Choose a range of card numbers or Marked Cards Only, then Print or Save PDF. Only fields print — a button is a thing you press and a widget is a thing that sounds — and a field with more text than its box prints all of it rather than cutting the last verse. Report is HyperCard's Print Report: choose a field to Group By and a field to Total, and the stack's cards are listed under each value of the grouping field with a subtotal apiece and a total at the end. Cards with nothing in the grouping field are listed under Unassigned, and text that isn't a number counts as nothing — the same arithmetic as the web report page. Print sends it to a printer, and Save PDF writes it to a file. Print Report… beside them lays the cards out the way the web's Print report does: tick the fields to print, choose Columns (a row per card) or Labels (two or three cards to a row, the first field as each label's heading), give it a title, and turn on Marked Cards Only if you like. A preview lists the cards it will print; the pages carry the title at the top and Page n of m at the foot. Email Cards… sends cards to someone, as the web card list's Email selected does: tick the cards (the one you're on starts ticked, and Select picks all or the marked ones), enter the address, and Send. The email has each card's title and non-blank text fields in card order, without layouts, widgets, scripts, recordings, or attachments. Only editors can send cards. Canvas is the same freeform board as the web: every card sits where someone put it, and cards nobody has placed fill a grid below the arranged ones. Scroll to move around, choose a zoom, and type in the search field to keep matching cards bright while the rest dim. Turn on Arrange to drag cards into place — they snap to the same grid the web uses, and the board scrolls again when you turn it off. Line Up puts every card in stack order in a grid, and Undo takes back the last arrangement. Arranging needs Authoring, and positions are shared with everyone who can see the stack. Map draws the same diagram as the web — every card placed, with an arrow along each link — and filters it by link kind; turn Diagram off for the list of connections, broken links, and cards nothing connects to. Choosing a card in either view opens it. Table in the card toolbar lays the stack out like the web table view: each card is a record and each background field a column. Choose Columns, filter by text or tag, tap a column heading to sort without changing the stack's order, edit text cells in place, Add Record, or Export CSV of what is shown. Import CSV reads a spreadsheet back in: choose a comma- or tab-separated file whose first column is named Card Name, and each other column fills the field of that name. Leave Match Rows By on Add Every Row to add a card per row, or pick a field to update by: a row whose value in that field matches a card changes that card instead of adding another. Rows that can't be written are listed and change nothing. Tap a record's name to open its card. Finds filters records by a field containing text and saves that search by name to run again; saved finds are private to you, even in a shared stack. Views saves the whole arrangement — the columns you chose, the filter, the tag, and the sort — under a name, and puts the table back that way when you choose it again; these are the same saved views as the web data workspace, so one saved on a phone opens on the web, and they too stay private to you. Find and Replace in the table changes exact, case-sensitive text in every card name and field of the stack. In Settings, the stack's owner also has Automations…, the same rules as the web: each sends a signed webhook after someone submits the stack's public form, either for every submission or only when a form field equals a value or is not empty. Add one with a name, an HTTPS webhook URL on a public address, and a signing secret; turn a rule off to pause it, or swipe to delete it. The secret can't be shown again after you save, and a rule shows only the host it posts to. Rules run only while the public form is on. The owner also sees Google Calendar: once the stack is connected, Sync Now sends dated cards to your primary calendar as all-day events and brings back date or title changes made to those events, and Disconnect… removes Wyldcards' access while leaving the events in place. Connecting finishes on the web, because Google returns you there: choose Connect in Browser, connect in Stack Settings, then come back and choose Check Again. In Settings, Snapshots… saves a copy of the whole stack and restores one later as a new stack, leaving the original unchanged.

Commands (⌘K on a Mac or an iPad keyboard) is the web's command launcher: type part of a name to find any card action, any card in the stack, or another stack to open, then press Return for the top match or choose one. Exact and word-start matches rank first, then letters in order, such as "nc" for New Card, with the matched letters highlighted and a label saying where each one comes from. With an empty search your recently used commands come first, and actions that wouldn't work right now, like painting a stack you can only view, are left out.

Back and Forward beside the Next arrow retrace your jumps within the stack, as the web's jump arrows do: going to a card from Find, the Storyboard, the table, a link, or Recent Cards is a jump, while Previous, Next, and the marked-card arrows step in order and aren't. Recent Cards beside them shows the cards you have visited in this stack, newest first, up to forty-two; choose one to go there. On a Mac or an iPad keyboard, ⌘[ and ⌘] go back and forward and ⌘R opens Recent Cards. Both lists belong to the app for this session, and opening another stack starts a new trail.

On a Mac or an iPad, Open in New Window on a stack (touch and hold it, or right-click) opens it in a window of its own, and Compare With in a card's More menu opens another stack beside the one you're in, as the web's Compare does. Each window is a complete, independent workspace: move through its cards, use its tools, and edit where you can.

Scroll Stack shows every card in order side by side, each keeping its layout, with nothing else on screen; Open Card goes to the interactive card and Back returns to the one you came from. Editors can turn on Arrange Cards and move a card earlier or later with the arrows above it.

Practice runs the stack's cards as a focused session, as on the web: choose card order or shuffle and one to ten rounds, then Start Practice. A bar under the toolbar shows where you are; Complete and Continue moves on, and End Practice stops. The session is kept on the device, so it picks up where you left off when you open the stack again (a stack that has gained or lost cards since starts afresh), and it never changes the cards, so it works on stacks shared with you as a viewer.

On a card, Mark builds a working set, and Previous Marked and Next Marked step through it, wrapping around. Turn on Marked Only in the Storyboard to see just that set. Marked Cards beside them works on the whole stack at once: Mark All Cards, Unmark All Cards, and Delete Marked Cards…, which asks first and then deletes them for good — a stack keeps its last card, so that one stays whatever is marked. Bookmark in the card toolbar saves the card to your Bookmarks, and Presenter Notes opens the card's private notes, which only people who can edit the stack see. Card Details renames the card and sets or clears its date. The card toolbar's More menu (grouped into the Actions menu on a narrow screen) has Comments, where anyone who can open the card can read and post, History, which restores a saved version after keeping the current state as another version, Duplicate Card and New Card with Same Layout, Templates (make a card from a saved card template, save the current card as one, or delete one), and Archive Card… and Archived Cards for taking cards out of the stack and bringing them back. Present shows one card at a time on a dark backdrop; swipe or use the arrow keys, Space, Page Up, or Page Down to move, and editors can open the presenter notes beside it. The Navigator lists the whole deck beside the card (on an iPhone it opens as a sheet) so you can jump to any card, and when cards are marked, Present Marked plays just those, in their order. Card Details also has Can't Delete and Don't Search, and Settings has the stack's Protect Stack options; the app follows them, so a stack that can't be modified or is limited to Browsing or Typing turns off editing, and Typing or above is needed to type into fields. Open This Stack in the Editor, beside the card design, starts people who can edit on its first card in Edit mode; viewers still browse. Recordings in the card toolbar lists the audio kept with the card: play any take, Record a new one with the microphone, or add an existing audio file. Rename or delete a recording from its menu; deleting a recording can't be undone. Some web recordings, such as WebM and Ogg files, can't be played in the app. In Edit mode, the part inspector has the web app's Hidden box, a Style section for font, size, bold, italic, alignment, colors, corner radius, and border, and a Button Style choice from Standard to Popup Menu; set a Family for radio buttons and Options for a popup. In Browse, check boxes, radio buttons, and popups remember what you pick, and hidden parts stay out of sight until a script shows them. Buttons and cards run their scripts in the app as they do on the web: tapping a button runs its on click script (and the card's, background's, and stack's handlers above it), and openCard scripts run when a card opens. The app runs them on the card's own web page, out of sight, so the same rules apply — on a stack someone shared with you, only scripts its owner approved run, and only after you choose Run Scripts from the card toolbar's More menu (Stop Running Scripts turns them off again). A script's answer and ask questions appear in the app, the cards it goes to open in the app, and a script that opens another web page asks you to use Full Workspace. Without a connection the app keeps working from the copies it saved of the stacks, cards, and parts you opened: an Offline bar says so, field edits wait on the device and are sent when the server answers again (Try Again checks straight away), and an edit to a field someone changed meanwhile asks Keep Mine or Use Theirs. Signing out deletes the saved copies. Cards show their paint layers, the background's picture and then the card's, behind their parts, and image widgets show the stack's uploaded images; Paint changes those pictures. Choose a widget's Widget Type in its inspector. With a keyboard, press or for the previous or next card while you are not typing in a field, Cmd + F to find in the stack, Cmd + N for a new card, and Cmd + E to switch Edit mode; on a Mac, a new window is Cmd + Shift + N. Choose your account name in the toolbar to set the Appearance (System, Light, or Dark) and Text Size — both saved with your account, so the web opens the same way — to Change Password…, or to sign out; the app asks for a new password straight away when your account requires one. For anything the app doesn't have yet, such as teams, open Full Workspace from the Stacks toolbar. Components in the inspector saves the selected part under a name with Save as Component…, and puts a copy of any saved component on this card or its background, in any stack you can edit; changing a copy doesn't change the component. A multiline field's Ruled Lines toggle in the inspector draws HyperCard's lines under its text, as the web's does. In Edit mode, the Part selector at the top of the inspector picks any part on the card, topmost first, so one hidden under another or too small to tap is still in reach. A button's Destination is a chosen card, the Previous Card, or a Random Card, as on the web; a card destination with no card chosen runs the button's script. A Linked Cards field shows a chip for each linked card — tap one to open it, even in another stack, or × to unlink it — and Link a Card finds another by name in any stack you can open (or only the stack chosen under Link Cards From in the inspector); a linked card lists what links to it under Linked from. Under a card, Links here names the cards whose buttons or card-link fields point at it, each a tap away, and Related Cards… connects a card to others in the stack without choosing a direction, shown on both cards and in the Map. When Field Equals adds a route — a field, the value to match, and the card to go to — saved with Save Route and taken whenever the field matches. A button's Visual Effect and Effect Speed — dissolve, wipes, scrolls, iris, zoom, barn door, venetian blinds, checkerboard, to black or to white — play when it changes cards, through its link or its script, and are skipped when the device asks for reduced motion. Tapping a line of a list field tells the card's scripts, so an index card's wyldcards:select handler — the Songbook's Contents, say — goes to the song you tap.

Changes lists every edit to a field or a card's name, newest first, with who made it, when, and the words removed and added. Put Back returns one to how it was before (and offers Put Back Anyway when it has changed again since), and Undo My Last Change and Redo — also ⌥⌘Z and ⇧⌥⌘Z on a card — take back or bring back your own latest change without writing over anyone else's.

Keep Offline in a stack's menu downloads the stack for reading without a connection, including cards, paint layers, uploaded images, and recording lists; recordings download on Wi-Fi. Kept stacks refresh while connected, and you can download again or stop keeping them offline. Open stacks also cache nearby cards unless Low Data Mode is on. Offline Find and Search use the copies on this device. Recordings made or added offline remain under Waiting to Upload until the server responds, then upload automatically; signing out removes saved copies after warning about unsent work.

Offline, you can also make and rearrange cards, not only type into them. New Card adds a card straight away, with its background's fields ready to type into and record on, and Capture adds its card at the end of the stack with the note in a field you can keep editing. Delete Card, Move Earlier and Move Later, Mark, and renaming in Card Details work too; as on the server, a stack keeps its last card and Can't Delete cards stay. These card changes are sent first when the server answers, in the order you made them, and then the edits and recordings on the new cards. The Offline bar counts them with everything else waiting. Import keeps the file on the device and makes the stack when you're back online. Download Markdown… writes the file from the copies on this device, and says so; cards never opened here have only their names. Export Stack… needs a connection. New Stack works offline as well: the stack joins your list with its first card, ready for new cards and captures, and is made before anything in it is sent. Stack Settings, Pin to Top, Archive Stack, and Move to Trash show in the list straight away and are sent when you're back online. Trash, Archived Cards, and Editions show the list as you last saw it; an edition opened here before still opens, and restoring, deleting, unarchiving, and managing editions come back with the connection.

🔎 Find & Search

Press Cmd + F on a card (or the Find button in the toolbar) to search the stack you are in. Matches show as you type — a card's name, the text of any field, a button's label — and clicking one goes to that card. Cmd + G walks to the next match and wraps at the end; hold Shift to go back. Esc closes the bar and gives your browser's own find back.

Search & commands in the user menu (or Cmd + K, or the search box on All stacks) searches every stack you own as you type: matching cards appear under Cards, after any matching commands, showing the stack and the text that matched. Choose Search all stacks for “…” at the end of the list to open the full results page, which looks across every stack you own at once, grouped by stack, with the stack's own name and description matched too. It also searches your private presenter notes and audio attachment titles or filenames; audio bytes and scripts are not searched. Use several words to narrow results: they stay in the order you typed, but can cross punctuation, extra text, or line breaks. Archived stacks are searched and marked as archived; stacks in the trash are left out. The in-stack Find bar leaves presenter notes out so viewers cannot see private notes.

From a script, wyldcards.find("chorus") does the same thing and goes to the first match — pass false as a second argument to look without moving, and call wyldcards.findAgain() for the next one.

Search & Commands

Search & commands is one keyboard-first, Raycast-style box for moving around Wyldcards and finding what you wrote. Choose Search & commands in the user menu, click the search box on All stacks (or press / there), or press Cmd + K from anywhere in the app.

Once you type two or more letters, the cards, notes, and attachments that contain them appear under Cards, after the matching commands, with the stack name and the matching text; choose one to open that card. The last result, Search all stacks for “…”, opens the full search page with every match grouped by stack, and is the top result when no command matches, so typing and pressing Return always searches.

With an empty search the launcher shows your Recent commands first, then Current stack actions, then On this page: every enabled button, link, save, download, and stack action on the current page. Only the first few page controls are listed until you type, with a count of how many more there are; repeated controls, such as a Home tab and a Home footer link, appear once, and a page button that does what a launcher command already does, such as a Bookmarks or Recent… button, is left to that command. Search for the action you need instead of finding it on screen, then press Enter to use it. Commands that have their own keyboard shortcut, such as New card, Find in stack, Recent cards, Message Box and Edit card, show it beside the command so you can skip the launcher next time. As soon as you type, every matching command from every group is ranked into one list with the matched letters highlighted and a small label showing where each one comes from, so the best match is always at the top. Exact and word-start matches rank first, then fuzzy matches such as "nc" for New card; commands you have used recently rank a little higher. While editing a card, the launcher also lists every widget type, so searching for "piano", "image", or "add widget" adds it directly. The launcher does not list its own Search & commands button or repeat the stack actions it already offers.

Typing part of a stack's name opens that stack directly, including stacks shared with you. Choosing New stack creates an untitled blank stack immediately and opens it for editing. The launcher also includes common destinations such as importing a stack, Search, My stacks, Bookmarks, Archive, Templates, Customize home, Help Center, Keyboard shortcuts, and appearance settings. Choose Find a stack to browse your active stacks by name, or New card in a stack to pick any stack you can edit; it creates a blank card and opens it in Edit mode. Inside either list, press Backspace on an empty search, or click the label beside the search box, to return to the full command list. While viewing a stack, New card creates one immediately after the current card. Other available stack actions include Capture note, Find, Edit, Card list, Print, and Map. The available actions reflect your sign-in status and enabled features.

The launcher also opens stack views that normally live inside the View menu: Storyboard, Canvas, Outline, Table view, and the card Navigator. It can take an owner to Stack settings without opening Share first. Global commands include Trash, Account settings, and Automations & API; administrators also see Product analytics. Type any part of an action or related word to filter the list; for example, search for "search help" to open the Help Center. Matching is flexible, the strongest matches rise to the top, and the search bar always shows how many commands are available. Use Up and Down Arrow, Tab and Shift + Tab, or Control + N and Control + P to select a result, Page Up or Page Down to jump through a longer list, Home or End for the first or last result, and Enter to open it. You can also point and click a result. Use the clear button, the Clear search link when nothing matches, or Esc to clear a search. When choosing a stack, Esc, or Backspace on an empty search, returns to commands; press Esc again to close the launcher and return focus to where you were. Cmd + K also closes it.

Feature Finder

Choose Help in the header to look up any feature by name or by a related word, such as "csv", "shuffle", or "speaker notes". Before you type, the menu suggests topics for the page you are on, for example Edit Mode and Fields, Buttons & Widgets while editing a card, or Printing on the print page, along with the features you looked up most recently on this device. In the iPhone, iPad and Mac apps, Help in the account menu searches the same topics.

Results show the best matches first with a one-line description, and matching words are highlighted. Close spellings still match, so "metronom" finds the metronome widget. Press Enter to open the top result, Up and Down Arrow to move through the list, and Escape to clear the search or close the menu. Every search ends with More in the Help Center, and when no feature matches, choose Search the Help Center to look through the full text of every guide.

Quick Capture

Choose New card beside Edit to add a blank card after the current one; it opens in Edit mode. In Edit mode, New card is the first toolbar control and can also start from the same layout, copy the current card, or use a template. Choose Capture to save an idea without opening the editor first. Or add Quick Capture under Widgets in Arrange on All stacks; it appears under your Home card, where you choose its destination stack. It needs at least one stack you can edit; if you do not have one yet, the widget links you to create it. Add a title and an optional note; Wyldcards creates a normal new card with the title as its name and the note in a text field. The card opens in Edit mode afterward, ready for you to add images, recordings, links, or anything else.

Marked Cards

Use More > Mark on a card you can edit to make a working set: tonight's songs, scenes to revise, or cards ready to print. Marked ‹ and Marked › appear when a stack has marks and move through that set, wrapping around. Choose Unmark to remove the current card. Scripts can do the same with wyldcards.goMarked('next') or wyldcards.goMarked('prev').

Jump History

Use the and controls beside the card arrows to go back and forward through card jumps made with buttons, card-link fields, related cards, links here, or the Map. They appear once there is a jump to retrace. This is separate from Prev and Next, which follow stack order, and it does not replace your browser's own Back and Forward history. The trail lasts for this browser session and stays with its stack or public share.

Page Transitions

Supported browsers gently fade between pages and in-page updates. Wyldcards automatically turns this motion off when your device or browser requests reduced motion; other browsers navigate normally.

✨ Visual Effects

A button can change cards with one of HyperCard's visual effects. In Edit mode, select the button and choose a Visual effect in the inspector — dissolve, wipe left/right/up/down, scroll, iris open/close, zoom open/close, barn door, venetian blinds, checkerboard, to black or to white — and a speed from very slow to very fast. The effect plays whichever way the button moves: a card link, a conditional route, or wyldcards.go(...) in its script. The iPhone, iPad and Mac apps play button effects too, and set them in the inspector.

Scripts can name an effect directly: wyldcards.go('next', 'dissolve'), wyldcards.go(3, {effect: 'wipe left', speed: 'slow'}), or wyldcards.visualEffect('iris open') before any navigation. The Message Box understands visual effect dissolve followed by go next. Effects are skipped when your device asks for reduced motion, and in browsers without view transitions cards simply change.

🏠 Home Stack

HyperCard began at Home, a stack like any other, and so does Wyldcards: signing in, the Wyldcards logo, and the Home tab all open your Home stack. It is also in the user menu, the launcher, on All stacks, and in scripts as wyldcards.go('home') (the Message Box understands go home). It is made for you the first time from four cards: Home, whose stack list widget shows your stacks with buttons for a new stack, the templates, Recent cards and bookmarks; All stacks, whose all stacks widget holds the whole arranging page (the dock, folders, bulk selection, Archive and Trash) and is where every link to All stacks opens; Preferences, with radio buttons for the appearance (they always show the appearance in use, even when you changed it from the account menu or on another device) and buttons for the text size, plus a notes field; and Links, buttons to the Help Center, shortcuts, search, your account and the stack arranging settings. Its menu bar gets a Home menu from the stack script.

The stack list follows how you arranged All stacks: docked stacks first (marked 📌), a stack group as a folder that opens its substacks, then stacks others share with you, marked Shared. Its last tile opens All stacks. Once you have more than eight stacks, a Filter stacks box sits above the tiles: type part of a name to narrow them, press Enter to open the first match (or, when nothing matches, to search every card), and Escape to clear it. The arrow keys move between tiles, and Up from the top row returns to the filter. On a phone, where a card shrinks to fit the screen, the stack list and the All stacks card are shown at full size under the card instead, and the card says so; turn the phone sideways on a wide enough screen, or press Edit, and they go back onto the card. Recent… on Home shows the cards you visited in all of your stacks, each labelled with its stack, rather than Home's own cards. The widgets you choose under Arrange appear under the Home card.

Press Edit and change it: move the buttons, add cards, give it a paint layer, write scripts. The stack list widget can go on any card of any stack, and always shows the reader's own stacks. Home is protected against deletion so go home always has somewhere to land, and it cannot be shared, because shared stacks run no scripts. Under Start on in Arrange you can open a different stack when you sign in instead; if you archive or trash Home, signing in opens All stacks.

Scripts on any card may call wyldcards.setTheme('dark') and wyldcards.textSize('larger') (or a percentage, or 'reset'), which is how the Preferences card works.

🎨 Paint Tools

Every card has a picture behind its parts, and so does every background: HyperCard's paint layers. Choose More > Paint on a card of your own stack to open the tools over the card. Choose Card or Background (a background picture shows behind every card that uses it), then a tool: pencil, brush, eraser, line, spray can, rectangle, round rectangle, oval, bucket fill and text. Shapes can be Filled with a colour or one of the patterns. Select drags a rectangle and Lasso draws around a piece; drag either to move it, or press Delete to erase it. FatBits zooms in on the pixels. Undo steps back, Save keeps the picture (Done saves too), and Clear erases the whole layer.

Pictures print, appear on the storyboard, in previews and on public pages, and travel in an exported stack. Nothing on the picture can be clicked, so a script cannot be attached to it; put a transparent button over it instead, as HyperCard did.

🧾 Report Layouts

Below the grouped report (Data → Report) is Print report, HyperCard's Print Report dialog: tick the fields to print, choose Columns (one row per card) or Labels (two or three cards to a row, the shape of a sheet of address labels), give it a title, and print only the marked cards if you like. Browsers that support printed page margins add the title at the top and Page n of m at the foot of each sheet.

📋 Scripted Menus

A stack script can add its own menus to the toolbar, as HyperCard 2's create menu did: on openStack wyldcards.menu('Songs', ['Sort by title', '-', 'Shuffle']). Picking an item sends menuPick to the card, so on menuPick[detail.item is 'Shuffle'] wyldcards.go(wyldcards.random(wyldcards.card().count)) answers it. A dash makes a separator; an item may be {label: 'Save', disabled: true} or {label: 'Loop', checked: true}. wyldcards.deleteMenu('Songs') removes one, wyldcards.menus() lists them, and they go away when you leave the stack.

🗂 Recent Cards

Press Cmd + R on a card, or View > Recent cards, for HyperCard's Recent window: small pictures of the cards you have visited in this stack, newest first, up to forty-two. Click one to go there. The list is kept by your browser for this session, so it is yours alone; a card deleted since simply drops out. On your Home stack the window spans every stack you visited this session, and each picture names its stack. Scripts can open it with wyldcards.go('recent').

🔒 Protect Stack & Card Info

Protect stack, in a stack's settings, is HyperCard's dialog of the same name. Can't modify makes the stack read-only for everyone, you included, until you clear it. Can't delete keeps it out of the trash. Private access makes the stack password gate you as well as your collaborators. Limit user level sets the most anyone may do here: Browsing reads, Typing types into fields, Authoring edits the layout, Scripting edits scripts too. Scripts still run at every level, and the Message Box and script editors appear only at Scripting.

Each card has two flags of its own in the edit bar's Card menu, HyperCard's Card Info: Can't delete, which makes Delete card and Archive card refuse it (also from Data tools and the API), and Don't search, which keeps it out of Find and Search. A field can carry Don't search too.

▶ Message Box

Press Cmd + M on a card of your own stack (or choose More > Message) to open HyperCard's Message Box: one line where you type a command and press Return. It understands a few HyperTalk spellings — go next, go to card "Chorus", find "solo", put 5 into field "count", field "count", sort by name, show "hint", hide "hint", beep, play "c4q d e", speak "hello", flash, mark cards by finding "yes", unmark all cards, visual effect dissolve, push card, pop card, move card to stack "Songs", copy card to stack "Songs", move marked cards to stack "Archive" — and anything else is run as _hyperscript, with me set to the card, so wyldcards.setField('count', 0) works too. The result appears beneath the line; and recall earlier commands.

Watch turns on the Message Watcher, a log of the messages the card sends as it sends them — openCard, idle, wyldcards:select and the rest — which is the quickest way to see what a script can listen for. The Message Box runs in your browser only, like your scripts, so it is not offered on shared, public or published stacks.

Card Tags

In Edit mode, choose Card > Tags in the edit bar to add the current card to one or more named tags. Type a new name to create a tag and add the card at once. Use Browse beside a tag to see only its cards; tags stay inside their stack and do not change card order.

☎ Contacts

An address book is a stack like any other. Clone Contacts from New stack → Templates and you get a live Directory plus one card per person or place, with fields for name, company, phone, role, email, address and notes — the crew, the band, an agent, a venue.

The Directory stays alphabetized and opens the selected contact. Use Copy to start a similar entry or + New person for a blank one. Cmd + F finds anyone by name, company or number, the card list shows the book at a glance, and the stack exports and imports with the rest of your work.

Add fields it hasn't got, or take out the ones you don't want: press Edit and change the background, and every card changes with it.

🔐 Passkeys & Sign-in

Sign in with a password or, once you have registered one on the account page, with a passkey (Touch ID, Face ID, a security key). If a passkey prompt cannot start because the service is busy, wait a minute and try again. Forgotten your password? The sign-in page has a reset link that emails you.

📱 Install as an App

On a phone or desktop browser, use Install app in the account menu (or your browser's "Add to Home Screen") to run Wyldcards as a standalone app. The install guide keeps keyboard focus inside it; press Esc or choose Got it to close it. Once you're signed in, the header's sync status shows whether changes are Saved, Syncing, waiting, offline, or need attention. When a connection drops while a card is open, text fields, checkboxes, lists, and checklists save their latest value on this device and sync automatically when you reconnect. Select the status when changes are waiting to retry immediately. Moving cards, changing layouts, uploads, sharing, and deletes still need a connection, so they cannot replay unexpectedly later. If you were signed out while changes waited, the status says Sign in to sync; they are sent once you sign in again.

✈️ Keep a Stack Offline

To open a stack with no connection, choose Keep Offline… from a card's More menu while you are connected. Wyldcards downloads every card of the stack, with its pictures and paint layers, to this browser; recordings are not downloaded. The menu then reads Kept Offline… ✓, and choosing it shows how many cards are on the device and when they were saved, with Update Now and Remove from This Device. A kept stack keeps itself current while you are connected: opening a card refreshes its copy, and the whole stack downloads again when cards are added or removed, or after a few hours.

Without a connection, open a kept stack from its bookmark, its Home Screen icon, or the On this device list on the "You're Offline" page, which also reopens the page you wanted as soon as the connection returns. Previous, Next, and the card navigator move through the kept cards. The banner says you are reading the copy kept on this device, and what you write in fields, checkboxes, lists, and checklists waits on the device, stays visible as you move between cards, and is sent when you reconnect. If someone else changed the same field meanwhile, your draft is not forced over theirs: it waits under Review saved drafts, named by field, card, and stack. Pages that are not kept say so instead of doing nothing, and adding, moving, or deleting cards, layout changes, uploads, and sharing still need a connection. If a connection is too slow to answer, a kept card opens from its copy after a few seconds; choose Open the live card in the banner for the current version.

Copies belong to the account that made them. Signing out, or the sign-in page opening after a session ends, removes every kept stack from the browser; edits still waiting are kept for your next sign-in. Keep Offline needs a browser that supports installed web apps; the iPhone, iPad, and Mac apps have their own Keep Offline in each stack's menu.