When you build a sign-up form, a customer table or a CRM screen, placeholder rows like "John Doe" rarely reveal what will go wrong. Turkish names do. Names such as Çağla, Özgür, Şule or Yağız and surnames like Yıldırım, Öztürk or Kılıç contain characters that trip up encodings, search filters, slug generators and case conversion. This random name generator gives you hundreds or thousands of them in seconds.
Every record has five fields: id, ad (first name), soyad (last name), eposta (email) and sehir (city). The email is built from an ASCII version of the name plus the row number, for example [email protected], so every address is unique and none of them can reach a real inbox. Cities come from a list of well-known Turkish cities such as İstanbul, Ankara, İzmir and Çanakkale.
How to use: Random Turkish Name Generator
- Enter how many people you need in Number of records (1 to 5,000).
- Choose a Copy / download format: JSON, CSV (Excel-compatible UTF-8) or SQL (MariaDB / MySQL INSERT).
- If you picked SQL, type the SQL table name your INSERT statements should target.
- Click Generate test data and review the first 100 rows in the Data preview.
- Use Copy to put the full result on your clipboard, or Download to save it as a file.
Example: 3, Çağla, Öztürk, [email protected], Eskişehir
Where random Turkish names are useful
A list of believable names makes a prototype feel finished and, more importantly, puts real-world strings through your code. QA engineers use it to fill registration forms, product teams use it in clickable demos, and developers seed local databases with it.
- UI demos and screenshots that look realistic without exposing real customers.
- Sorting and search tests: does "Çelik" sort after "Cetin" or at the end of the list?
- Case-conversion checks: the dotted İ and dotless ı break naive toUpperCase and toLowerCase calls.
- Training sessions and tutorials where every participant needs the same kind of sample users.
Why Turkish characters are a classic i18n test
Turkish is famous among localization testers. Uppercasing "i" in a Turkish locale gives "İ", not "I", and lowercasing "I" gives "ı". Code that compares strings with the wrong locale, or databases that use a Latin-1 column instead of utf8mb4, quietly corrupt these names. Running a few thousand generated rows through your import, export and search features is a fast way to catch mojibake such as "Ç" before your users see it.
What the tool does not generate
There is no gender filter, middle name, phone number, street address or national ID number. Those fields were left out on purpose so the output can never be mistaken for, or matched to, a real person. If your schema needs extra columns such as a signup date or a UUID, use the mock data generator in this category and combine ad, soyad and eposta with the other types.
Use fake names responsibly
Generated names are for testing, design and education. Do not use them to open fake accounts, pose as someone else, write fake reviews or deceive anyone. Testing with synthetic people instead of copied customer records is also the safer route under the GDPR and Turkey's KVKK.
Frequently asked questions
Are these real people?
No. First names and last names are picked independently at random from short lists of common Turkish names, so any combination is a coincidence rather than a reference to a real person. The email addresses use example.com, a domain reserved for documentation that cannot receive mail.
Can I generate only female or only male names?
Not at the moment. The tool has no gender filter, and many Turkish names such as Deniz, Umut or Duru are used for any gender anyway. If you need a gender column, add it yourself after exporting, for example with a spreadsheet formula.
Will the same name appear more than once?
Yes, especially in large batches. The name lists are intentionally compact, so duplicates of first name and last name pairs are normal and are actually useful for testing how your app handles people with identical names. Every email is still unique because it includes the row number.
How do I open the CSV in Excel without broken characters?
Choose CSV (Excel-compatible UTF-8) before downloading. The file is saved with a UTF-8 byte order mark, which tells Excel to read ç, ğ, ş and İ correctly. If you paste copied text instead of opening the file, use Data > From Text/CSV and choose UTF-8 as the file origin.
Can I import the names into MySQL or MariaDB?
Yes. Pick the SQL format, enter your table name and run the INSERT statements. The tool does not write a CREATE TABLE statement, so create a table with id, ad, soyad, eposta and sehir columns first, ideally with the utf8mb4 character set.
Do I need an English name generator instead?
If your app only ever shows US or UK names, a dedicated English name generator is a better match. Choose this tool when you are building for Turkish users, testing localization, or simply want non-ASCII names to stress-test your encoding.