Skip to main content
The card is what buyers see before they pay: the cover, the name and one line in the catalog grid, then the gallery, the description and the tags on the item page. All of it lives in the editor’s Basics section. spd publish only sets the first name and summary; the rest is up to you. The draft saves itself as you type. Preview card shows how the item will look in the catalog.

​
Fields

The fields that are wrong turn red when you press the publish button, and the toast says how many to fix.

​
Name and summary

Say what it does and what makes it different. Buyers scan the grid; the name and the summary are all they read there. Leave the price, “cheap” and “undetected” out of the name: the price is already on the card, and promises about bans get items rejected.

​
Description

Answer what a buyer would ask in a DM before paying. A structure that works:
Headings with ### , lists with - , links as [text](https://…). Check Preview before publishing.
  • Describe only what’s really there. “Doesn’t match the description” is a reason to report an item, and a reason for a dispute and a refund.
  • If the script asks for ffi or filesystem, say what for: buyers and the moderator will want to know.
  • No links to other shops, payment chats, or “write me for a discount”. Deals outside the market break the rules and aren’t covered by disputes.

​
Tags

Tags are how people find the item in search and how the catalog filters it. Use the words they type: legit, rage, esp, aim, hvh, faceit, hud. Tags are lowercase; a leading # is dropped. Search understands common spellings in both languages (aim and аим, esp and вх), so one form of each word is enough.

​
Screenshots

​
Upload and order

  • Press Add and pick the files. JPG, PNG or WebP, up to 10 MB each.
  • Large pictures (over 2 MB) are shrunk in your browser before upload: to 2560 px on the long side, saved as WebP. You don’t need to resize anything yourself. Animated pictures are uploaded as they are, so they must fit in 10 MB.
  • The first screenshot is the cover. Drag a screenshot to the front, or press Make cover on it. On a phone, press and hold a screenshot until it lifts, then drag. With the keyboard, focus a screenshot and move it with the arrow keys.
  • A screenshot is saved once it has uploaded. If one fails, the editor names the file and says why.

​
What to shoot

  • The cover: the result, not the code. The ESP in a real round, the HUD in action, the menu page your script adds. It’s shown small, so one clear subject beats a collage.
  • Then the details: the script’s menu, its settings, a close-up of what it draws.
  • 16:9 at 1920×1080 or more. Full-screen game captures fit the card best.
  • Your own work only. The spurdo! menu and the game with your script running.

​
What not to put there

  • Other cheats’ or other authors’ interfaces.
  • Ads, watermarks of other shops, links, contacts, prices.
  • Your account details: nick, Steam profile, balance, emails.
  • Promises such as “undetected” or “no bans” on the picture.
Screenshots that don’t match the item, or show someone else’s interface, get the item rejected or taken down on a report.

​
Next steps

Prices, discounts and grants

Free, forever, by term, discounts and promo codes.

Publishing and moderation

What the button does and why it can refuse.