Frequently asked.
Fully answered.

No. You can make a plain donation as a guest. An account is useful for your dashboard, followed projects and preferences. A reward can require contact information even when you do not create an account. Keep the private donation link and confirm a guest email when requested.

Creating an account and preparing project drafts are free. Publication and received project donations have the separate costs described on the pricing page and in the project guide. You do not pay a publication contribution just to explore or support a project.

Email verification confirms control of the inbox used for your account. You need it before using the protected maker workspace. The verification message contains a private, time-limited link; it does not request a payment or wallet recovery words.

Allow a little time for background delivery, check the exact address and look in spam or junk. On Check your inbox, request a new link if needed and use the newest message. The site limits repeated requests and tells you when to wait.

If the account is not verified, sign in and request a new link from Check your inbox. A link expires after one hour, is single-use and can be replaced by a later request. If you already verified successfully, sign in normally instead of reopening the same link.

Your display name is the public name used around your profile and projects. A username is a unique account handle using the permitted letters, numbers and underscores. The sign-up form explains the length and format. Your email is the address you use for normal password sign-in.

Two-factor authentication is available for ordinary accounts and is not automatically required just because you join. If you enable it, its code or an unused recovery code becomes part of the relevant sign-in and security checks. Keep the recovery codes private.

Choose Forgot your password? on the sign-in page, enter the account email and open the reset message. Follow the time-limited link and choose a new password. A password reset does not remove an enabled authenticator, so keep its recovery method available.

No. Lightning sign-in is for a wallet that has already been linked to an existing account. Create and verify the account first, then link the wallet under Security. LNURL-auth proves control of the linked wallet key; it is not a donation or payout setup.

They are separate settings. A linked LNURL-auth wallet is a sign-in method. The Lightning wallet setting stores the validated receiving destination for your projects. Connecting one does not automatically configure the other.

The account email and security settings are not public profile fields. Public names, profile information and published projects can be visible. Delivery information is shared with the participants who need it through the private donation flow; read the privacy page for the full policy.

Following saves a convenient connection to the project in your account and can make you eligible for relevant update notifications, depending on your preferences. It does not make a payment or reserve a reward. Supporting a project is a separate action.

The on-site notice and the email have separate delivery states. Check the topic in Email preferences, the verified inbox and spam folder. Mail is processed in the background. For a guest donation, finish its email confirmation step if requested.

Automatic no-reply emails are notifications and their replies are not read. Use the private donation conversation for a reward or delivery question, and the site support contact for an account or platform problem. The email action link usually takes you to the relevant page.

SatsGarden and its maker Mila de Vries are fictional tutorial examples. The images and screenshots explain the real interface, but their example references, addresses and QR codes are not live payment or account details to use. Choose an actual published project on the site when you want to support a maker.

Start with a verified account, a clear title and pitch, a cover image, a real story and a funding plan. You can save a private draft before it is complete. A validated owner payout wallet and the required checklist are needed before submission for publication.

A draft is not the same as a published project. Use the owner preview to review saved content while you prepare it. Do not share a private editor URL as the public launch link; wait for the published state and use the public project URL.

For an eligible new project, the one-time publication contribution is 2,100 sats after approval. Editing and updates are included afterward. A project marked as waived follows its own publication status and controls. See Pricing for the current policy.

Saving does not automatically publish a project. Complete the checklist and submit it, then wait for the review result in your workspace and notifications. If changes are requested, read the note, update the relevant section and submit again.

No. The publication contribution is a platform payment associated with publishing the project. It is separate from supporter donations and does not count as a donation to the project.

An overall target is optional; the editor supports 0 for open funding. A target helps explain a plan, but it is not an automatic all-or-nothing condition. Separate donation goals can identify specific purposes when you want that level of detail.

The checklist checks the introduction, story, cover, funding plan and validated maker wallet. Active funding options also need valid prices and clear commitments. Open the missing checklist item, complete it, save and check again. Extra photos do not replace a missing required field.

You can add up to 9 gallery images. Open Media, drag items into your preferred order and save the project. On touch devices use the gallery drag gesture or handle. Remove an existing image if you need to make room for a different one.

The editor supports the link and upload options shown in Media, including supported YouTube or Vimeo links and direct MP4/WebM video links. You can have a main video and up to three extra project videos. Read the current upload limits beside the file input and add a useful title and description.

The update form has separate email choices for followers and eligible backers. Choose them intentionally. Actual delivery also respects the recipient and their preferences, and a public update remains available on the project page. Publishing the same update repeatedly is not a useful way to force delivery.

Yes. The owner funding control can pause new donations and reward orders separately from the visibility of the project page. Existing invoices may still be paid and earlier commitments remain. Re-enable funding through the same owner control when you are ready.

Closing uses a distinct owner action and asks for the relevant outcome or fulfilment information. A closed project is kept as a record and its public information becomes read-only. Existing reward commitments and private delivery conversations still need to be handled. Read the confirmation before using the close action.

No. A project can accept plain donations without a reward. Offer a reward only when it makes sense and you can describe the commitment clearly. Recognition, custom work, digital items, physical items and packages have different practical requirements.

Yes. Edit the option in Funding options and upload or replace its own image. Choose an image that represents that particular commitment, then save and inspect the public detail view. The project cover and a reward image are separate fields.

An option can have a capacity, and eligible pending payments can temporarily reserve places. Packages can share component stock with other offers. Use the editor's actual remaining availability rather than counting only the visible cards. Saved commitments remain attached to existing donations.

You can change the offer for future donations through the editor, but existing donations keep their recorded amount and reward terms. Communicate material practical changes with affected supporters through their private conversation rather than relying on a silent public edit.

A package combines other funding options into one offer. Read or configure the included components and quantities, and check their shared availability. The package should make the total commitment and delivery expectations clear before a supporter pays.

Open the private page for the confirmed donation and use its conversation or requested details action. The owner can also start from Supporters and delivery. Keep the discussion attached to the correct donation reference and do not put shipping details in a public message.

A sat, short for satoshi, is a unit of bitcoin: 100,000,000 sats equal 1 bitcoin. This platform shows donation and reward amounts in sats. Approximate currency hints are informational; check the actual sats amount and any wallet fee before approving a payment.

Use a wallet that supports Lightning payments and has enough available balance for the donation and any fee it charges. Follow the wallet provider's own instructions for adding funds. A Lightning invoice is different from a Bitcoin on-chain address.

The current minimum plain donation is 1,000 sats. A reward has its own displayed minimum and can cost more. The checkout checks the current policy and the selected offer before preparing the invoice.

The platform fee is 5% of a project donation and the maker allocation is 95%. Network costs covered by the platform come from its share. Your wallet may show a separate payment fee of its own. The payment screen shows the allocation before you pay.

Use Keep my name anonymous in the donation form to hide the name from the public contribution list. This does not remove payment records or the practical information needed to fulfil a reward. Read the privacy information for the distinction between public anonymity and private processing.

The maker needs a reliable way to arrange the reward and notify you about its private page. A product option can require contact information even when a plain donation does not. Confirm a guest address when requested so private access is not mailed to an unverified inbox.

Use the retry action on the form; your choice is preserved. A failed preparation can be replaced by a fresh attempt. If the payment provider is unavailable, the connection must recover before another attempt can produce an invoice. First check whether your wallet already paid an earlier invoice.

Keep the original private donation page and reference. Let the page check the backend and contact platform support if confirmation does not arrive. Do not pay again merely because a screen has not refreshed. Include the reference, approximate time and wallet status in a private support request.

Prepare a current request through the project flow rather than repeatedly scanning an expired QR. If a wallet reports a completed payment, investigate that existing payment first. The website keeps references and recorded commitments so a late or uncertain payment can be reviewed.

For a guest, the private link is an important way back to the receipt, email confirmation and reward conversation. A public project URL or donation reference alone is not the same access. Keep the link private and use the backup-access option offered on the donation page.

Start with the maker in the private conversation for the donation and include the reference. Use platform support for account access or a payment-system problem. The donation terms explain the platform policy; a request for review or a refund is not proof that money has been returned. Follow the confirmed result.

No automatic all-or-nothing condition is created simply by displaying a target. Read the project's funding plan and any specific reward commitment before contributing. A goal describes a target or purpose; it is not by itself a guarantee of a particular outcome.