Back to home

Diss Track Writing Workbench

Plan a friendly battle rap, write and check your bars, then take the complete lyrics into the song studio. Local writing tools, not an AI lyric generator.

Open the workbench
Diss writing workbench

Write the rivalry before you write the track

Set the structure, write bar by bar, and get live counts for syllables, rhyme letters, runtime and delivery density before you hand the brief over.

This page writes nothing for you: every number here is computed in your browser from your own bars, the draft stays in this browser, and the studio is where a song is actually made.

Brief and shape

These fields become the brief handed to the studio. The more concrete they are, the more the first draft has to work with.

One sentence for what the track is about

The teammate, rival or team who is in on it

One per line — details are what survives into lyrics

Names, places, anything you do not want mentioned

Ground rules

Tick all four and the brief states that the ground rules were confirmed.

Structure

Change the numbers, then rebuild: bars you already typed keep their place.

Sections match the numbers above

Write the bars

One bar per line. The letter is the rhyme the tool detected and the count is an estimated syllable load; empty bars stay in the structure without counting as written.

No bars written yet — pick a section and start the first line.

Verse 1

0/120:30
  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9
  10. 10
  11. 11
  12. 12

Hook 1

0/80:20
  1. 13
  2. 14
  3. 15
  4. 16
  5. 17
  6. 18
  7. 19
  8. 20

Verse 2

0/120:30
  1. 21
  2. 22
  3. 23
  4. 24
  5. 25
  6. 26
  7. 27
  8. 28
  9. 29
  10. 30
  11. 31
  12. 32

Hook 2

0/80:20
  1. 33
  2. 34
  3. 35
  4. 36
  5. 37
  6. 38
  7. 39
  8. 40

Live analysis

Write a few bars and this panel fills in syllables, rhyme and runtime.

Export and hand-off

Brief sent to the studio

341 / 2000 characters

Add a topic first so the brief says what the track is.

Your complete lyrics and brief travel together. Review or edit them before creating the project, and keep editing before generating music.

How to use this tool

What makes a diss track land

A diss track is a song built on a rivalry: two people, two teams, two friends who will not let one lost bet go. The form comes out of battle rap, and it lives or dies on craft. A setup that raises an expectation, a punchline that flips it, and a hook everyone can shout are what make people replay a diss track instead of wincing at it.

Craft is also what keeps it friendly. The best diss tracks aim at a performance, a team record, or a running joke — never at who someone is. This page is a free writing workbench for that kind of track: the panel above holds the brief, the structure, and the bar grid, and it measures what you typed. Everything below explains the craft those numbers are checking. A name, a rivalry, and one true detail are enough to start.

The workbench above

  • Brief and shape. Topic, who the target is, mood, the details that must land, words to keep out, a rhyme scheme (AABB, ABAB, AAAA, ABBA, or free), a delivery focus, a tempo, and the four-rule confirmation.
  • Structure. Opening bar, verse count, bars per verse, hook bars, and optional intro, bridge, and outro. Change a number, rebuild the sections, and bars you already wrote keep their place.
  • Write the bars. One bar per line in a numbered grid, with insert and delete per bar, duplicate and delete per section, and Sync hooks to the first hook.
  • Live analysis. Bars written, estimated syllables for each bar, rhyme groups and the scheme detected in each section next to the one you chose, density against your delivery focus, and runtime estimated from your tempo.
  • Checks and flags. Bars carrying a heavy syllable load, bars that look under-filled, bars repeated word-for-word, repeated filler terms, and hooks that drifted from the first.
  • Punch placement. Four-bar landings that arrive without a reversal word, plus a second-person versus third-person count — two of the rules below, measured.
  • Release check. A local keyword list for identity, threat, private-information and harassment terms, plus phone and email patterns. It reads words, never context, and it is not the studio's moderation: a hit only means "read this line again".
  • Export and hand-off. Copy the lyrics or brief, download a .txt file, or continue into the studio with your complete lyrics. Review them before creating a project that saves every written line.

The workbench writes nothing for you: no lyrics are generated, the draft stays in this browser, and the studio is where a song is actually made.

Nothing here researches anyone for you. The studio writes from the brief, the details, and the lyrics you supply; it does not pull in a rival's posts, messages, or private information, and it will not write harassment on your behalf.

Ground rules that keep a diss track safe to release

Read these before you write a single bar. They are the difference between a track your group chat quotes and a track you have to apologize for.

  • Pick a target who is in on it. A roast works when both sides agreed to play. Going after a private person who never opted in is bullying with a beat.
  • Attack the contest, not the identity. Nothing about race, ethnicity, religion, disability, gender, sexuality, or body. "You missed the last four penalties" is fair game; "you are built like a bus seat" is not.
  • No threats and no violence. Hyperbole about a losing streak is fine; anything that reads as a credible threat is not.
  • Stay out of private life. No addresses, workplaces, phone numbers, medical details, family members, or anything a person did not put in public themselves.
  • Keep claims obviously playful or true. Accusing someone of a crime you cannot prove is a defamation problem, not a punchline.
  • Keep the language release-ready. Slurs, sexual content, and hate are rejected by content-safety checks, and those checks apply to prompts and lyrics alike.
  • Have one other person read it first. If a line is funny to you and to them, it will probably land with the audience too.

These rules mirror the platform's Acceptable Use Policy, which governs prompts and lyrics on OnePromptSong. If a request is built around harassing a real person, it will be refused, and repeated attempts can end an account.

The workbench asks you to confirm four ground rules beside the brief and records that confirmation with it. Its Release check then scans your bars for identity, threat, private-information and harassment terms, plus phone and email patterns. It is a keyword list, not a judgement call, and it cannot tell a joke from an attack or read a line in context — treat a hit as an invitation to read the bar again, and keep the human reader in the loop.

Build the lines: setup, punch, turn

Bars rarely fail because the insult is weak. They fail because the setup is missing, so the punch has nothing to land against.

  • Set up in two bars, land in the next two. Give the listener a premise they can follow, then hit on the last stressed beat of the second bar.
  • Misdirect, then flip. Let the crowd assume one ending and give them the other. "They call you the brains of the group — so explain the group chat you forwarded" works because the first half sets a compliment.
  • Be concrete. "Your fantasy team has finished last three seasons running" outlasts "you are trash", because the audience can picture the table.
  • Turn it on yourself once. A self-aware bar buys the room's sympathy and makes the next punch harder.
  • Keep the target in second person. "You" keeps it a duel; "he" turns it into gossip about someone who is not in the room.
  • Cut the third joke in every set. The first two are usually the good ones, and the audience hears a shorter verse as a more confident one.
  • Do not explain the punchline. If a line needs a footnote, rewrite the line.

The workbench measures two of these directly. Punch placement lists the four-bar phrases that land without a reversal word and counts second person against third person, so a verse that starts talking about the target instead of to them shows up as a number before an audience hears it.

Rhyme, rhythm, and the hook

Rhyme is a delivery system for the joke, not a decoration.

  • Couplets (AABB) are the default for a battle verse. ABAB and internal rhyme make a verse sound denser, and breaking the pattern on the punch makes it louder.
  • Reach for multi-syllable rhymes — "moves slow" against "whose throw" — when the simple ones run out, and let assonance carry a line where no perfect rhyme exists.
  • Count syllables per bar. Eight to twelve at around 90 BPM keeps the verse speakable; write short lines so you still have breath on the punch.
  • Never invert a sentence to save a rhyme. "For the loss of the game you are to blame" sounds like a tax form.
  • Write the hook short: four to eight words. It does not need the rival's name. A call-and-response line — "that's what they said?" — gives a crowd something to answer.
  • Place the hook after every verse, and keep it identical each time. Variation is what makes a hook forgettable.
  • Sixteen bars is enough. Three verses on the same angle is a memo, not a song.

The workbench covers the measurable half of this list: pick a scheme and it reports the scheme it detects in each section, estimates syllables per bar against your delivery focus, estimates runtime from your tempo, and flags a hook that drifts from its first wording.

Prompt example — a friendly battle between two friends:

The last clause of that prompt is doing real work. Telling the studio what to exclude keeps the track in roast territory and keeps the request clear of content checks.

Reusable diss-track prompts

A team roast for the end-of-year party:

A five-a-side rivalry anthem:

Swap the details, keep the exclusions. Continue with these lyrics transfers every written line and section together with your brief. Review the imported lyrics before creating the project; they are saved as your own draft, not replaced with an AI draft.

From lyrics to a finished track

  1. Open Start with your story and describe the rivalry in the idea field: who it is about, what actually happened, and the tone you want. Starting a project is free; you sign in so the song is saved to your account.
  2. Fill in the brief: genre, mood, vocals, occasion, and each concrete detail on its own line. Details are what give the punchlines something to hit. The brief's genre list is pop, acoustic, country, R&B, and indie — rap is not one of the options, so choose the closest feel, describe the beat you hear in the idea box, and let the lyrics carry the battle.
  3. Generate a lyrics draft, then rewrite it — or replace it with the bars you wrote in the workbench. Copy lyrics or the .txt export moves them across, and nothing reaches the music step until you approve it.
  4. Generate two versions as an A/B pair. One version costs 10 song credits and a fresh pair costs 20; generation usually takes a couple of minutes.
  5. Listen to both, choose the take, then download the full MP3 and share it through a private link.

Credits come from a monthly plan or a one-time pack; new accounts may receive welcome credits to help finish a first song, and the amount varies. Pricing lists plans, pack sizes, and how long credits last.

One limit is worth stating plainly: OnePromptSong does not import or convert existing audio, remove vocals, or export stems, and there is no public API for submitting prompts programmatically. The studio's job is turning your brief and lyrics into a finished song you can preview, download, and share privately.

For more writing craft, the journal covers prompt and structure work in depth. To see the full flow first, start at the home page or open the studio, and continue with pricing.