English Abbreviations: Texting, Email and Spoken Forms

Separate the names once and everything else sorts itself out.

• Contractions — I’m, don’t, it’s. Fully standard in both speech and writing, and the default in conversation. Not using them is the marked choice.
• Reductions — gonna, wanna, gotta, lemme. These are pronunciations written down, not spellings. Native speakers say them constantly and write them almost never.
• Acronyms and initialisms — ASAP, FYI, ETA, DIY. The language of work email and documents. They barely appear in casual speech.
• Text speak — idk, btw, tbh, omw. Messaging only. The moment one lands in an email it reads as careless.
• Clippings — app, info, fridge, exam, ad. These stopped being abbreviations years ago. Saying refrigerator in full now sounds odder than the short form.

Almost no one gets into trouble here by not knowing a meaning. They get into trouble by using the right form in the wrong place: wanna in a message to a manager, Please advise ASAP to a friend, tbh on a presentation slide. All three are correct English and wrong for the room.

Which is why a meaning alone is not enough to store. idk = I don’t know is half a note and it will come out in the wrong place. idk = I don’t know, messaging only is a usable one. Write the place down next to the meaning, every time.

Learners often say I am, do not and it is in full, usually on the theory that it is more correct. It is correct, but in conversation it does one of two things: it makes you sound like a textbook, or — more often — it makes you sound like you are stressing that word on purpose.

That second effect is the important one, because in English the uncontracted form is an emphasis device.

• I’m not angry. — ordinary negative.
• I am not angry. — pushing back on something you just said.

Speak in full forms all day and you sound like someone perpetually contradicting the room without meaning to. Contractions are the neutral setting.

The next thing worth knowing is that some contractions are ambiguous by design:

• ’s = is or has. He’s coming (is) / He’s gone (has).
• ’d = would or had. I’d like coffee (would) / I’d already eaten (had).
• ’re, ’ve and ’ll only ever mean one thing.

You cannot hear the difference, and you do not need to: the verb that follows settles it. After ’d, a past participle means had and a bare infinitive means would. That one rule removes most of the confusion these cause in listening.

And there are places where contracting is simply not allowed. These are worth memorising as rules rather than feel:

• A sentence cannot end on a positive contraction. Yes, I am. — never Yes, I’m. The same applies mid-sentence at a clause end: I don’t know if he is, not …if he’s.
• Negative contractions are fine in that position. No, I’m not. / No, he isn’t. Both work.
• CVs, applications, academic writing and formal notices spell everything out. Blogs, marketing copy and workplace chat contract by default. Email sits between the two, and matching whatever your correspondent does is a reliable rule.

Ain’t deserves its own note. It covers am not, is not, are not and have not, and it is classified as non-standard. It is alive in song lyrics and inside fixed phrases (If it ain’t broke, don’t fix it), but a learner producing it deliberately almost always lands wrong. File it as recognise-only.

These are the best known English abbreviations and the most frequently misused. The whole rule fits in one line: they record how a phrase is pronounced, and they are not a written form.

A native speaker says gonna in essentially every casual sentence about the future. That same person writes going to in an email without a second thought. Neither version is wrong — speech and writing simply differ here. When a learner writes gonna in a report, the effect is not informality, it is the impression of English learned entirely from the internet. In a text message to a friend it is fine.

The flip side matters more, though: in speech you should be using them. Pronouncing I am going to call him word by word breaks the rhythm of the sentence, and your listener hears emphasis you did not intend.

They also come with grammar that lists rarely mention. These forms do not fit everywhere:

• gonna only works before a verb. I’m gonna leave is fine; I’m gonna the store is not English. Only the future going to reduces — going to meaning actual movement never does.
• wanna also needs a verb after it. I wanna go, yes. I wanna a coffee, no — with a noun it stays I want a coffee.
• gotta comes from have got to, and in speech the have disappears entirely: I gotta go. In the third person the ’s tends to stay: He’s gotta go.

The same family runs much wider than those three, and these are the ones that pay off fastest in conversation:

• lemme = let me — Lemme check.
• gimme = give me — blunt, so friends only.
• dunno = don’t know — I dunno.
• kinda / sorta = kind of / sort of — used constantly as softeners.
• ’cause = because — mid-sentence it reduces almost every time.
• hafta = have to, oughta = ought to, I’mma = I’m going to (very colloquial).

The usable summary: all of them when speaking, most of them when messaging, none of them in an email.

Text speak moves fast, so lists go stale. Memorise a list from ten years ago and you will sound like someone’s uncle. Here is what is actually in circulation.

Seen daily

• idk — I don’t know
• btw — by the way
• tbh — to be honest
• ngl — not gonna lie (does the same job as tbh)
• omw — on my way
• rn — right now
• imo / imho — in my opinion / in my humble opinion
• nvm — never mind, jk — just kidding
• np — no problem, ty — thank you
• wyd — what are you doing?, hbu — how about you?
• ikr — I know, right? (agreement)
• smh — shaking my head (disbelief)
• fr — for real (strong agreement)
• tldr — too long, didn’t read, used before a summary
• dm — direct message, also a verb: Just dm me.

Forms that date you

• ROFL, or LMAO in capitals — lowercase is the default now, and capitalised LOL reads as theatrical.
• u, r, ur, l8r, b4, 2day — leftovers from character limits. Using them now reads as 2008.
• xoxo, plz, cuz — alive, but tied to specific people and contexts rather than general use.

Two things matter more than the list itself.

First, lol no longer means laughter. It is a softener — it takes the edge off the sentence it is attached to. Can you send it again lol is not funny; the lol is there so the request does not read as nagging. When something is genuinely funny people write lmao, haha, or send an emoji. Treating lol as a laugh is the single most common misreading of it.

Second, shortness itself carries tone. In English messaging, a one-word reply with a full stop (Ok.), a capital K, or any short sentence closed with a period reads as displeasure almost universally. To keep the same content friendly you either lengthen it (ok sounds good!) or add a softener (ok np). That is the paradox of this whole category: abbreviations exist to save effort, and past a certain point saving effort is read as withholding it.

This is the informal end of the language. The slang that shares the same messages is collected separately in this guide to English slang.

Workplace abbreviations are convention rather than fashion, so they last. Learn them once and they stay useful.

• ASAP — as soon as possible
• FYI — for your information, FYR — for your reference
• EOD — end of day, COB — close of business, EOW — end of week
• OOO — out of office, WFH — working from home, PTO — paid time off
• ETA — estimated time of arrival, used for deliverables as well as people
• TBD — to be determined, TBC — to be confirmed
• N/A — not applicable, EOM — end of message
• cc / bcc — also verbs: I’ll cc you.
• RSVP — reply to confirm attendance, ATTN — marks the intended reader
• 1:1 — a one-on-one meeting

The pair that causes the most trouble is e.g. and i.e. Both are Latin and they do opposite jobs.

• e.g. = for example. It opens a sample from a larger set. Bring something warm, e.g. a jacket. A coat would also qualify.
• i.e. = that is. It restates what came before, exactly. The deadline is Friday, i.e. the 30th. Friday and the 30th are the same thing.

If you hesitate, read them aloud in your head as “for example” and “in other words” and the right one becomes obvious. Both take two full stops, and in American usage a comma follows (e.g.,).

Meanings aside, the real failures in this category are about tone:

• ASAP reads as pressure. Downward from a manager it is routine; upward, sideways or to a client it can be rude. A specific time is safer and sounds more professional anyway — by 3pm today, by EOD Thursday.
• FYI alone can read as passive-aggressive. A forwarded message whose entire body is FYI. is easily taken as “you should already have seen this”. One extra clause neutralises it: FYI, no action needed.
• Do not mix text speak in. idk, tbh and btw in a work email are a misstep; write I’m not sure, frankly and by the way. Internal chat is the exception, and following whatever your colleagues already do is safe there.

The sentences these abbreviations sit inside are covered in more depth in business English phrases. The abbreviations are components; the frame around them does more work.

Knowing every word in a sentence and still not catching it is almost always the same problem: English is not pronounced the way it is spelled, and course audio is recorded carefully enough to hide that. Study only from clean recordings and the gap stays exactly where it was.

What happens in real speech goes far beyond gonna. The frequent ones:

• What do you → whaddya. Whaddya think?
• What are you → whatcha. Whatcha doing?
• Did you → didja, Would you → wouldja
• could have → coulda, should have → shoulda, would have → woulda
• a lot of → alotta, out of → outta
• let me → lemme, give me → gimme

The coulda group is worth extra attention. The have vanishes so completely that the phrase sounds like could of — which is why native speakers themselves write could of by mistake. Store the two separately: coulda for listening, could have for writing.

The more useful insight is that the reductions are predictable. English stresses content words — nouns, main verbs, adjectives — and flattens function words: auxiliaries, prepositions, pronouns, articles. So the pieces that disappear are nearly always the ones carrying the least meaning. Put the other way round: what you failed to hear was usually what you did not need. Dropping the goal of catching every syllable makes listening measurably easier on its own.

There is only one way to train this. Recognising a reduction on paper does not make it audible — you have to produce it yourself, because an ear rarely picks out a sound the mouth has never made. Say Whaddya think? ten times and it starts appearing in speech you hear afterwards. The wider listening routine is in English listening practice, and the sound-making side in the English pronunciation guide.

Taking the whole list at once produces nothing usable. Take one item per place instead.

1. Make contractions your default in speech. This is a habit change rather than new vocabulary, so it costs nothing to adopt. Contracting I am, do not, it is and I will everywhere immediately removes the stiffness from spoken English. On its own it outperforms everything below.

2. Learn reductions for listening first, speaking second. Five is enough to change what you can hear: gonna, wanna, kinda, lemme, dunno. Keep writing them out in full.

3. Pick five texting abbreviations, not fifty. idk, btw, tbh, omw, np cover most of what a casual conversation needs. The rest only need to be recognisable when they arrive — your reading list and your writing list do not have to be the same size.

4. Take only the work abbreviations your own job touches. If you never work remotely, WFH is dead weight. If you schedule things constantly, EOD, ETA and TBD come up weekly. Choosing the five that match your week is the whole exercise.

5. Keep two tone rules. No text speak in email, and a specific time instead of ASAP. Those two prevent most of the damage this category causes at work.

6. Then try them on a person and watch what happens. The hard part of an abbreviation is never its meaning — it is whether it is too casual for this particular moment, and no list tells you that. Lists also never mention which entries have quietly gone stale. Dropping them into relaxed conversation with a native speaker on CoffeeTalk settles both questions fast: if the other person absorbs it and keeps going, the form is live; if they pause or ask, cross it off. Alternating chat and voice with the same partner also makes the written-only and spoken-only boundary obvious without anyone explaining it.

One expectation worth correcting at the end. Heavy use of abbreviations feels like fluency and reads as the opposite — overuse mostly reveals where someone learned their English. What actually sounds native is not the count but the ability to pick the register the situation calls for. Someone who writes in full sentences by email and clips everything in chat comes across as far stronger than someone deploying tbh in both.