AI presentation maker for Pakistan: real .pptx decks from one prompt, in English or Urdu

Making a presentation in Urdu, or in a mix of Urdu and English, involves a set of problems that do not exist when you make one in English. Fonts substitute wrongly. Text direction fights with the layout. Bullet markers land on the wrong side. Line breaks fall in the middle of joined letterforms. And the deck that looked correct on your laptop opens broken on the lab machine you have to present from.

Most of these are solvable and none of them are obvious. This covers what actually goes wrong with Urdu in PowerPoint files, how to generate a bilingual deck that survives being opened somewhere else, and the checks to run before you present.

The font problem, which causes most of the damage

Urdu is set in Nastaliq — cursive, steeply sloped, with letters that change shape by position. The Nastaliq font almost everyone means is Jameel Noori Nastaleeq, and it is not installed by default on Windows, macOS or most Linux systems.

When a presentation asks for a font that is not present, the software substitutes silently. There is no warning. Your Urdu is then rendered in whatever Arabic-capable font is available, which is usually a Naskh style: horizontal, angular, correct in its characters and visibly wrong to any Urdu reader. This is the single most common way an Urdu deck arrives looking amateurish, and the author frequently never sees it because it renders correctly on their own machine.

There are two robust fixes. Embed the fonts in the file — PowerPoint on Windows supports this and it is worth the file size. Or, if you cannot guarantee the presenting machine, export to PDF, which bakes the glyphs in and cannot substitute. For a presentation you are handing in or presenting from someone else's computer, PDF is the safe answer even though it costs you editability.

Direction, alignment and line breaking

Urdu runs right to left, and a text box has to be told that. A right-to-left paragraph in a left-aligned box produces text that starts at the wrong edge, with punctuation at the wrong end of the sentence — an error every Urdu reader spots instantly and most authors miss because they are reading the words rather than the layout.

Bullet and number markers belong on the right for Urdu content. If they are on the left, the paragraph direction was not set even if the text looks correct.

Mixed-direction lines are the hardest case and they are extremely common: an Urdu sentence containing an English term, a percentage, or a year. The rendering of that line depends on bidirectional text handling that varies between applications, which means a mixed line can look right in one program and scramble in another. Where you can, isolate English terms in their own text box or their own line rather than embedding them mid-sentence.

Line breaking is a subtler issue. Nastaliq words are cursive units, and a naive line-breaking algorithm can break inside one, splitting joined letterforms across two lines. Keep Urdu lines comfortably short rather than filling the box to its edge — it avoids the problem entirely and reads better anyway.

Layout: Urdu needs more room than you think

Nastaliq has significant vertical extent. The diagonal baseline means a single line of Urdu occupies more height than the same point size in Latin script, and descenders reach further. Line spacing that looks generous for English will look cramped for Urdu, and lines will visually collide.

Set Urdu at a larger point size than you would use for English, and increase the line spacing. As a starting point, roughly twenty percent more of each, then adjust by eye.

This has a consequence for how much you can put on a slide: an Urdu slide holds meaningfully less text than an English slide of the same dimensions. Plan for fewer bullets rather than smaller type, because reducing the size to fit is how you get Urdu that is technically present and practically unreadable from the back of a room.

Generating a bilingual deck

When you ask an AI to generate a presentation involving Urdu, being explicit about the language of each part removes most of the ambiguity. There are three common patterns and they need different instructions:

• Fully Urdu: headings and body both in Urdu script. Say so explicitly, and say Urdu script rather than just Urdu, or you may get Roman Urdu.
• English headings, Urdu body. Common in technical subjects where the terminology is English anyway. State it as a rule so it is applied consistently across every slide.
• Urdu content, English technical terms retained. This is usually what people actually want and almost never what they ask for. Say "keep technical terms in English" explicitly — translated technical vocabulary is frequently non-standard and can cost marks in an exam context.

The pre-presentation checklist

• Open the file on the machine you will present from, or on any machine that is not yours. This catches font substitution, which is invisible on your own computer.
• Check the alignment of every Urdu block. Text should start at the right edge, and bullet markers should be on the right.
• Read the punctuation at the end of Urdu sentences. A full stop that has jumped to the left end is the signature of unset paragraph direction.
• Look at every line containing both Urdu and English at full size. Mixed-direction lines are where scrambling shows up.
• Check for words broken across a line in a way that splits joined letters.
• If any of this is fragile and you cannot control the presenting machine, export to PDF and present from that.

Generating Urdu decks on RafayGen

RafayGen accepts the request in whichever language is easiest for you — "Ek 10-slide presentation banao solar energy pe" is a valid prompt — and produces a real, editable .pptx in the language you asked for.

Because the deck engine measures rendered text against its frame before handing you the file, the specific failure of Urdu overflowing its box, which the extra vertical extent makes more likely, is caught at generation rather than discovered when you open it. Slide counts are honoured, and content slides get varied layouts rather than every slide being a heading and five dots.

The font caveat above still applies and is not something any generator can fix for you: if you will present from a machine you do not control, check it there first or export to PDF.