Loading...

Selling Your Project

Put a price on your public page in credits — and why nobody can buy it yet: selling is not switched on.

Where the price is set

The price lives in the same in-place editor you already use for your public page — the one where you write the description, set the banner and choose whether to publish your source.

Two boxes, and you may fill in either, both or neither:

• the compiled .jar on its own;
• the jar plus the full source.

Leave both empty and nothing changes: the project is public and free, exactly as before. Fill one in and the price is saved with your page and the free download is held back from visitors — but selling is not switched on yet, so nobody can pay it either (see below).

Nobody can buy it yet

You can type a price and save it, and a visitor then sees the price and a Buy to download button instead of the free download — but buying is not switched on yet: pressing Buy for … credits answers Buying is not switched on yet and nothing is charged. A priced project is therefore on show but not downloadable by anyone until selling opens.

So do not count on sales until a later update switches buying on. If you want nothing shown in the meantime, keep the project private — see Your Project's Public Page.

The Sold tab in your Profile

Once one of your projects has a price, Profile gets a Sold tab. It is where your sales will be listed: how many, what buyers paid, the marketplace fee and what you kept. Until buying is switched on, it says so — Selling is not switched on yet — and your prices stay saved on your project pages.

The price itself is not set there. It stays in the page editor described above.

Prices are in credits — and the money is shown too

You type a price in credits, because that is what buyers spend. Underneath each box the app writes what that is in real money — Buyers pay about $… — worked out from the credit packs the site actually sells.

That is there to stop one particular mistake: asking 6.000 credits without noticing that is about $60.

What you are promising a buyer

Selling attaches a guarantee to your project, and it is worth reading before you set a price, because it binds you rather than us:

• a buyer can come back and download whenever they like, and never pays again;
• they always get your latest build, and only that one — each time you build, their download becomes the new jar and the one it replaces is deleted;
• their receipt survives you — their download does not, yet. Deleting the project, or closing your account, takes the buyer's file away, and no archived copy is kept anywhere. The purchase row stays; the jar goes.

So a bad build replaces the good one your buyer was using, and there is no older jar for them to fall back to. Test before you build, not after you sell — and if you are ever going to delete a project you have sold, tell your buyers first, because that download is the thing they paid for.

Pricing the source higher than the jar is the normal shape: most buyers want something that works, and the ones who want to read and change it are buying a different thing.

Where to next

• Next in Community: Getting Paid for a Sale
• Before you set a price: Your Public Project Page — What visitors see, and what they get for free.
• Making the listing look right: Editing Your Public Page — The editor the price boxes live in.
• If you are the customer: Buying a Project — The other side of it — what a buyer is promised.

6 of 13 in Community · Last checked 17 September 2026 · Previous: Editing Your Public Page