How to roleplay, in one sentence: you and a partner each play a character and write a story together, one reply at a time. You set the scene, you say and do what your character would, and you leave room for your partner to answer. That is it. Everything below is about doing it well enough that the story is worth coming back to.
This guide works whether your partner is a friend, a stranger on a forum or an AI character. Where the two are different, it says so.
Step 1: Pick a character with a reason to be there
A character needs a want, not a backstory. New roleplayers often write three paragraphs of history and forget to give the character something to do. Start with one line: who they are, and what they want right now.
- A smuggler who needs one more job to pay off a debt.
- A palace guard who just found a letter he was not meant to read.
- A new hire who suspects her boss is hiding something.
That want is what drives your replies. Backstory can come out later, in the story itself.
Step 2: Open with a scene, not a hello
Your first message decides how good the next ten will be. "Hi" gives your partner nothing. A good opener says where you are, what just happened and what your character wants from the other one.
| Weak opener | Strong opener |
|---|---|
| Hi, want to roleplay? | The tavern door slams behind me, rain dripping off my coat. "You're the one who sells maps. I need a way through the pass before sunrise." |
| You are a vampire. | I find you in the castle library, three hours after you told me to leave. "I came back for my sister. Tell me where she is." |
Notice the format: actions in asterisks, speech in quotes. That is the most common style in chat roleplay, and both human and AI partners read it easily.
Step 3: Write replies your partner can answer
End every reply with something to react to. A question, a choice, a threat, a door left open. "I nod." gives your partner a dead end. "I nod, then slide the map back across the table. 'Half now. Half when we're through.'" gives them a decision.
Good replies follow a simple pattern:
- React to what just happened.
- Do one thing or say one thing.
- Leave a hook.
Match your partner's length roughly. If they write two lines, do not answer with two pages.
Step 4: Never write for the other character
This is the one rule every roleplay community agrees on. You control your character. Your partner controls theirs. Writing "you agree and follow me" decides for them, and roleplayers call it godmodding. Write "I hold the door open and wait" instead, and let them choose.
The same goes for your partner. If an AI character starts writing your character's lines, a short note in brackets fixes it: [OOC: please don't write my character's actions]. Our guide to what OOC means covers that and the other terms you will see.
Step 5: Steer the story out loud
Stories drift, and that is fine. When you want to change pace, skip time or move somewhere new, say so. With a human partner, a quick out-of-character note works. With an AI partner, the same note in brackets works even better, because it tells her the request is from you and not from your character.
Useful steering notes:
- Skip ahead to the next morning.
- Slow this down, it is a slow burn.
- Introduce a problem: someone is following them.
How to roleplay with a person vs an AI
This is the decision most beginners face first, so here it is side by side. We build an AI roleplay app, Secret Desires, so treat this table as an interested opinion.
| Human partner | AI partner | |
|---|---|---|
| When you can play | When you both have time | Any time, as long as you want |
| Surprise | High, people bring their own ideas | Good, and better with a strong opener |
| Memory of earlier scenes | Depends on the person | Depends on the app; ours carries the story between chats |
| Pressure | Some, you are writing for someone | None, nobody judges a slow reply |
| Group scenes | Easy on Discord and forums | Mostly one-on-one |
Our honest take: if you love the social side of roleplay, a human community gives you something no app does. If you want a story that is there when you are, with a partner who stays in character and remembers what happened last week, an AI partner is the easier start. On Secret Desires she can also send a voice note when she delivers a line, or a picture of the scene.
Common beginner questions
How long should a roleplay reply be?
As long as it needs to be and roughly as long as your partner's. One to three short paragraphs is normal in chat roleplay. Fight scenes go shorter, emotional scenes can go longer.
What if I run out of ideas?
Add a problem. A stranger walks in, a storm hits, a secret comes out. Most stories stall because nothing is going wrong.
Do I have to be a good writer?
No. Clear beats fancy. Short sentences, clear actions and one hook per reply will carry a story further than pretty prose.
Start your first story
The fastest way to learn is to play one scene tonight. Pick a character with a world and a reason to need you, write a strong opener and see where it goes. Our roleplay AI page has fantasy, dark romance and slow-burn characters ready to start. For more opening lines, see our list of roleplay openers, and if you want swords and magic, AI fantasy is a good place to begin. For a look at why memory matters in long stories, read our roleplay explainer.

