Hungarian Website Translation: A Practical Guide


A Hungarian website that reads as if it were written in Hungary comes from three things: a source text prepared before anyone translates it, a translator who knows your industry’s terms, and a review of the live pages, not only the text file. Machine output alone rarely delivers that. At Wordsbyme, one experienced translator handles Hungarian, English, German and French website projects from source text to final check, using CAT tools (software that stores approved phrasing and keeps it consistent across pages).
This guide is for companies that need to put a site in front of Hungarian visitors: a US business entering the market, a multinational localizing a product, a medical or legal firm that cannot afford imprecise wording, or a game studio that wants its store page and in-game text to feel native.
TL;DR
Translation changes the words. Localization also adapts currency, date formats, measurements, legal details and visuals, so a Hungarian site usually needs both.
Decide before you start whether the site addresses visitors formally (Ön) or informally (te), and keep it the same on every page.
Hungarian words run long. Buttons, menus and chat windows built for English text need to be tested with real Hungarian strings.
Clean, frozen source text saves money. Errors in the English go straight into the Hungarian and have to be paid for twice.
Our per-word rates start at €0.05 for translation into Hungarian and €0.07 for translation into English, German or French.
Table of Contents
Translation or localization: what your site needs
The two words are often used as if they meant the same thing. Microsoft’s globalization documentation separates them: translation converts text into another language, while localization also adapts currency, date formats, measurements, cultural references, text length, legal requirements and visual elements. The same page notes that localization can happen without any translation, for example when US English is adapted for the UK.
For a Hungarian site, the practical split looks like this:
Element | Translation only | Localization |
Page copy, menus, buttons | Converted into Hungarian | Rewritten where a literal version sounds foreign |
Prices and currency | Unchanged | Shown in the currency Hungarian visitors expect |
Dates | Unchanged | Reordered to the year-month-day convention used in Hungary |
Names and addresses | Unchanged | Forms and fields adapted, such as family name first |
Legal notices | Words converted | Checked against requirements that apply to Hungarian visitors, such as GDPR |
Images and video | Left alone | Reviewed for embedded text, subtitles and cultural fit |
A brochure-style site with a stable product can often start with translation and add localization of the checkout, forms and legal pages. A webshop, SaaS product or game store page needs localization from the start, because those are the places where a visitor decides whether to trust you.
Prepare the source before anyone translates
Most cost and delay on a multilingual site comes from the source, not the translation. Microsoft’s guidance puts two early steps first: identify everything that needs translation beyond visible text, including images, videos, marketing material, FAQs, sample data and chatbots, and validate the source for consistent terminology before translation begins. Source errors slow the process and add retranslation cost.
A useful preparation checklist:
Inventory every string. Page copy is the easy part. Add form errors, confirmation emails, alt text, meta titles and descriptions, PDF downloads, cookie banners and chatbot scripts.
Freeze the English. Settle product names, feature names and the terms you use for the same thing. If your pricing page says “plan” and your checkout says “subscription,” the translator has to ask which you mean, or guess.
Write a short brief. One consultant on Hungarian sites, David Buka, recommends giving the translator the offer, the audience and the action you want the visitor to take, alongside the text itself. A button that says “Get a quote” is not translated word for word; the Hungarian version should be the phrase a Hungarian visitor expects to click.
Provide context. Screenshots or a staging link show the translator where a string appears and how much space it has.
Send existing glossaries. Any approved terms from earlier projects, product manuals or a previous site go in.
Our guide to briefing and choosing Hungarian translation services goes through what a good brief contains in more detail.
Decide on tone and address before you start
Hungarian has a built-in choice that English does not: whether to address the reader formally (Ön) or informally (te). It affects verb forms, so it cannot be fixed later with a find-and-replace. A style guide advice on multilingual brands says to define formal or informal address for each target language based on cultural differences and brand personality, set the tone, document allowed and avoided phrasings, and cover gender-related choices, because consistent tone strengthens brand perception.
In practice:
A law firm, clinic or financial service normally takes the formal register.
A consumer app or a game may reasonably use the informal one, if that suits the brand in English.
Whichever you pick applies to every page, every email template and every error message. A site that switches mid-checkout feels unfinished.
Writing this down as a one-page style sheet also helps whoever edits the site next year. If you are rebuilding the site at the same time, a structure that keeps text separate from layout, as in custom-built small business websites, makes it far easier to hold one register across every page and update it later.
Keywords: do not translate them literally
A Hungarian site also has to be found. Buka’s advice is that a literal translation of your preferred keyword is a starting point for research, not proof that customers search that way. The English phrase you rank for may have three Hungarian equivalents, and only one of them is what people type.
Ask the translator to propose the Hungarian term for each key page, then check those terms against what Hungarian visitors search for before finalizing titles and headings. The same applies to calls to action: an imported marketing phrase often reads stiffly, while a plain verb phrase for the action you want performs better.
Interface details that break Hungarian pages
This is where “translated” and “localized” diverge most visibly. A practical guide to the Hungarian market from a live-chat vendor lists several recurring problems:
Long words. Hungarian is agglutinative: endings stack onto a stem, producing words such as csomagautomatából (“from the parcel locker”). Chat windows, buttons and quick-reply chips that fit English can overflow and need testing with real Hungarian strings.
Special characters. The letters ő and ű are different from ö and ü. Older systems can mishandle them, so test fonts, databases, email templates and PDF exports.
Name order. Hungarians write the family name first. A form with “First name” and “Last name” in fixed positions can produce greetings that address the customer by their given name in the wrong slot.
Currency and dates. Prices should appear in forints for Hungarian shoppers, and Hungarian dates run year, month, day. Microsoft’s overview lists currency and date formats among the elements localization changes, with the US month-day-year order as its example.
Language independence. Hungarian is not related to the Slavic, Germanic or Romance languages around it, so visitors cannot fall back on a neighboring-language page. If the Hungarian version is missing or weak, there is no near substitute.
Addresses are a frequent trouble spot in checkout and contact forms. Our short guide to the Hungarian address format shows the correct order, which your form fields should follow.
A useful rule when you build or revise templates: give every button, tab and label room for text noticeably longer than the English, and avoid fixed-width containers. Designers who learn this on the first Hungarian page save a round of fixes on every later language.
Specialist content: technical, medical, legal and games
The more regulated or specialized the site, the less a generic approach works.
Technical and automotive sites depend on exact terminology: part names, specifications, units and safety text. Terms must match what Hungarian engineers and mechanics use. See our buyer’s guide to technical document translation for how those projects are scoped.
Medical and life-science sites carry the highest stakes. Microsoft’s overview states that linguistic validation is crucial for clinical trials, scientific instructions and legal documents, where processes such as ISO 13485:2016 for medical devices apply, and that translation memories and terminology lists should be reviewed by linguists, in-country marketing staff and subject matter experts. If your site has patient information, device instructions or trial recruitment pages, read our pages on medical terminology translation and clinical trial translation. Patient-facing wording that concerns a specific treatment should also be confirmed by the responsible physician or regulatory contact in your organization before publication.
Legal and financial sites need terms of service, privacy notices and disclaimers that match Hungarian legal vocabulary. Have your lawyer confirm which notices must be shown to Hungarian visitors; the translator then renders them precisely.
Games and software. Store pages, UI strings and community posts live or die on tone. Humor, idioms and references usually need re-creation, not conversion, and strings often contain variables (player names, counts) that interact with Hungarian suffixes. Give the translator context for every string, ideally a build to play.

Machine translation and post-editing
For large, low-risk volumes such as a help center or product catalog, a machine draft followed by human post-editing can be sensible. Buka’s view is that machine translation can prepare a draft, but a named reviewer who understands both the language and the offer should still check prices, units, dates, availability and promises. We offer this as machine translation post-editing in two levels: light, which fixes errors and makes the text understandable, and full, which brings it to publication quality. Choose full post-editing for anything customers read before they buy.
A review workflow that holds up under deadlines
Quality on a website comes from process, not heroics. An academic article in Terminologija describing a thirteen-step translation project process notes that QA tools create rules and checklists, QA includes terminology verification, and a final inspection checks against guidelines. The same analysis describes terminology compliance as checked from two sides: software matching the translation against the glossary, and a human reading the target-language content. The termbase grows from project to project and translation memory keeps term reuse consistent.
For a website, that translates into this sequence:
Terminology first. Agree on the glossary for product names and key terms before bulk translation.
Translate in a CAT tool. Repeated strings are translated once and reused, so a button label is identical on all forty pages.
Automated QA. Checks for numbers, tags, missing segments and glossary mismatches.
Read in context. Review the text on a staging site, not in a spreadsheet. This is where overflowing buttons, broken characters and awkward line breaks show up.
Functional test. Submit forms, run the checkout, trigger error messages and open the emails in Hungarian.
Final inspection. Compare against the style sheet and glossary.
Maintenance. Every new page or campaign goes through the same translation memory, so the site stays consistent.
Our article on translation project management lays out this kind of workflow in full.
What it costs
Website translation is priced per source or target word, and you can estimate a budget from your word count. Our published rates start at:
Service | Rate |
Translation into Hungarian | from €0.05 per word |
Translation into English, German or French | from €0.07 per word |
Machine translation post-editing, full | from €0.04 per word |
Machine translation post-editing, light | from €0.03 per word |
Localization is quoted per project, since it depends on how many formats, interface strings and visuals are involved. For example, a 10,000-word site translated into Hungarian starts at €500 at the published rate, before any localization work on forms, visuals or interface strings.
Perspective
Most website projects we see go wrong in the same place: the text was treated as a file to convert, not as a page a person will use. A Hungarian visitor does not care that the sentence is grammatically correct. They care whether it sounds like a company that works in Hungary. That is why we work as one translator from start to finish. You deal with one person who has learned your terms, your tone and your product, and who remembers on page 40 what was decided on page 3. With more than 15 years in the field and CAT tools that keep terminology consistent, we can take on high-volume sites without the quality drifting between pages. Deadlines matter on launches. We give realistic deadlines and keep to them, we are reachable after regular business hours when something urgent comes up, and your unpublished content stays confidential. Our advice is simple: settle the tone, freeze the source, and let the person who translates the site also read it in place before it goes live. Bernadett
Start a Hungarian website project
We translate into Hungarian from English, German and French, and into English, German and French from Hungarian, and we localize websites, software and video game content for technical, medical, legal, automotive, financial and marketing clients. Send us your site’s word count, the languages involved and your launch window, and we will tell you what the project takes. You can find our rates and contact details on wordsbyme.hu.

FAQ
How long does it take to translate a website into Hungarian?
It depends on word count, how specialized the content is, and how clean the source is. A small corporate site can move quickly, while a large webshop or a medical site with review steps takes longer. We give a realistic deadline per project, and urgent launches can be discussed outside regular hours.
Do I need to translate the whole site?
Not necessarily. Many companies start with the pages that drive sales or inquiries: home, product or service pages, pricing, checkout, contact and legal notices. Expand later, using the same translation memory so new pages match the first batch.
Should the Hungarian version be formal or informal?
Choose by brand and audience. Formal address (Ön) suits professional services, healthcare and finance, and informal (te) is common for consumer apps and games. What matters most is using one register everywhere.
Is machine translation enough for a website?
A machine draft can be a starting point, but customer-facing pages should be post-edited by a human who knows the subject and checks prices, units, dates and promises. Light post-editing suits internal or low-risk content, and full post-editing suits public pages.
Sources
Recommended

Comments