Product help
Create and approve your own keepsake artwork
Product team · Reviewed
Create, review and keep your wedding artwork
Open Keepsake studio and choose your wedding. Your workspace can make an original monogram, bring artwork it has permission to use, or create an AI portrait from a private photograph. Full workspace operators can work with these records. Joining a shared wedding does not reveal another business’s artwork or financial records.
Three ways to begin
Original monogram gives you botanical branches, an arch or a modern frame. Add names, initials, a date and a short line, then choose lettering, paper and decoration colors. Square and portrait compositions support a transparent background. Preview the actual vector composition and save a version to prepare its PNG. This is a deterministic original design, not an AI-generated portrait. The bundled font must support every character; for unsupported scripts, upload artwork using your chosen lettering.
My uploaded artwork retains your original JPEG, PNG or WebP privately. Confirm that you have permission to use the artwork and any likenesses it contains. Files can be up to 20 MB, 40 million decoded pixels and 12,000 pixels on each side, with at least 64 pixels per side. The prepared PNG strips original metadata, including embedded location data. A private note describes the artwork without adding that text to its image.
AI portrait from my photograph takes a reference of at least 256 pixels per side, art direction, a watercolor/editorial/illustration treatment and a square or portrait format. Review the reference filename, complete direction, model and exact generation fee. Confirm the transfer of the photograph and direction to OpenAI before starting. Usage spending must be explicitly enrolled and the workspace cap must cover the reservation. Physical ordering is separate.
Portrait generation is available only after provider and pricing activation. The integration uses the official Images API. A generative image can change details or likenesses, so inspect its actual output carefully before approving it. Saving a prompt does not count as a completed portrait.
Versions and exact-image approval
Every save retains its own definition, source fingerprint, renderer identity and actual output. Names, colors, directions and originals are not silently changed inside an old version. Simultaneous editors must review the latest design revision before saving.
Compare two ready versions side by side. Restoring a version creates a new latest version using the retained image; it does not call the portrait provider again, charge another generation fee, or inherit its former approval. Version history is paginated and exact version links remain available to authorized operators.
When an image is ready, choose Review this version. Check spelling, composition, likeness, dimensions and the image itself. Confirm rights and approve that exact image. The approved PNG can then be exported or selected for a physical keepsake. Checkout separately reviews the supported product, crop, effective resolution and price. A studio approval does not promise suitability for every print size.
Website use is a separate choice
After approval, choose an artwork section or a replacement hero image, and provide an accessible image description. Review the website address, current draft revision and whether the hero will be replaced. Explicitly approve creating an independent website copy.
The image is added only to the draft. Open the normal website editor, review and publish when ready. Revoking a studio approval does not secretly remove or unpublish a website copy; use the website editor to remove the copy or unpublish that site.
Recover processing without repeat generation
A saved job can be queued, generating, storing, complete, failed, canceled or uncertain. The page refreshes active work, and you can leave and return. Images and jobs remain private while awaiting processing.
- A queued portrait can be canceled before provider dispatch; its customer usage reservation is released.
- A confirmed provider rejection releases the reservation. Any later attempt needs its own request and cost review.
- If generation succeeds but storage fails, the provider result is retained privately. Storage retries reuse those same bytes, verify the artifact checksum and settle usage once. They do not generate another image.
- If the provider response is unknown, the attempt is held for reconciliation and never automatically regenerated. The workspace owner can record a reason and abandon an unresolved attempt after reviewing its provider reference. That releases the customer reservation; it cannot reverse a provider-side charge.
- A worker restart after provider dispatch can create the same uncertain hold. Do not assume that a network timeout means the provider never generated the image.
Missed worker wake-ups are recovered from persisted job state. Without storage and worker activation, queued output is not presented as ready. Local development uses explicitly enabled local fixtures and deterministic provider simulators.
Revocation, archival and retained copies
Revoking approval stops new downloads and new source orders from that approval. Paid orders retain their own approved production files and history; revocation does not cancel those orders. Use their normal order support controls.
Archiving ends all active studio approvals and cancels undispatched portrait requests. Version history and originals are retained. Recovering the design does not reinstate old approvals. General file cleanup cannot destroy artwork referenced by retained versions. Archive is not permanent erasure; any eventual erasure must separately account for retained orders and independent published website copies.
Developer access
The named-account /api/v1/keepsakes interface uses the same validation, permission, revision and request-receipt services as the editor. Source uploads have a separate bounded raw-byte endpoint. API keys cannot impersonate an artwork approver. Original bucket paths and signing credentials never appear in client responses; authorized image routes return bytes with private, no-store headers.