Hetzner lists several payment methods, but the options shown depend on country and account. If you are signing up from India, check your account rather than assuming a particular card, PayPal or bank option will be available.
Choose EUR or USD when you create the account: Hetzner says you cannot change the currency later. Separately, a server is only part of a YouTube Live setup. You still need a media source and a configured encoder to send video and audio to YouTube.
Check the payment methods shown in your account
Hetzner’s payment overview lists credit cards, bank or wire transfer, PayPal and SEPA direct debit. Its documentation also says methods vary by country. That means a list on a general help page is not a promise that every method will appear for an Indian billing address. The reliable check is the payment information available to your account during signup or in Hetzner Accounts.
Start by entering your accurate account and billing details, then review the available payment methods before ordering a server. If something you expected is absent, do not assume it can be enabled later; contact Hetzner support or choose from the methods actually offered to you. The Hetzner payment overview is the primary reference for how its listed methods work, but the account display is what matters for your specific case.
Hetzner lists Visa, Mastercard, American Express and UnionPay under credit card payments. It says card payments are automatically charged after an invoice is issued, except for UnionPay. That describes Hetzner’s process, not whether a particular Indian-issued card will be accepted or whether its issuer will authorise a transaction. Before relying on a card for a recurring service, check with your bank that international online and recurring payments are enabled. Google Cloud’s guidance notes that banks may decline its automatic recurring charges in India; that is a reason to ask your issuer a general question, not evidence about Hetzner’s own charge rules.
Hetzner describes bank or wire transfer and PayPal as manual payment methods. For a transfer, its instructions require your Hetzner customer ID in the payment reference. Ask your sending bank about its transfer fee, exchange rate and processing time: Hetzner’s overview does not establish what an Indian bank will charge. PayPal, if offered, is paid through Hetzner Accounts. Neither route should be treated as available until it appears for your account.
SEPA direct debit is for EUR accounts. It should not be confused with a normal debit from an Indian bank account. Consider it only if it is presented as an option and its eligibility fits your circumstances; do not plan a purchase around it based only on the general list.
Choose EUR or USD before you sign up
Hetzner lets a new customer account use EUR or USD. The choice has practical consequences: Hetzner says the account currency cannot be changed after creation. Switching requires a new account and moving products, so selecting a currency is not a casual setting to revisit when the first invoice arrives.
Before signup, compare the currency options against how you pay and keep accounts. Your bank or payment provider may convert a foreign-currency charge into rupees and may apply its own exchange rate or fee. Those costs are determined by that provider; do not assume the figure shown by Hetzner is the final rupee cost. If you keep a business budget in one currency, consider how foreign-exchange movements will affect your records and cash flow.
There is no universal right answer between EUR and USD for an India-based customer. Choose after checking which currency is supported by the payment method actually available to you, and how your bank handles that currency. The decision should be made before account creation, because Hetzner does not offer an in-place currency change according to its documentation.
If you already have an account, verify its currency in the account rather than opening a second one by mistake. Hetzner says a change requires a new account and product transfer. Before taking that step, review the migration implications with Hetzner: an account change is not the same as switching a display preference, and a live service may be affected while you move products or configuration.
Understand country-specific availability
Payment rules can depend on the account’s country, the provider’s supported methods and the issuer’s authorisation. These are separate checks. Hetzner decides which payment options it presents for the account; your bank or payment provider decides whether a particular transaction can be completed under its own controls. Success with a card for one service does not establish that it will work for another.
For a card, ask your issuer whether international online payments and recurring charges are enabled, whether it requires an extra authorisation, and how it handles a charge in your chosen currency. This is a sensible precaution, not a prediction that the payment will be declined. Google Cloud’s India billing guidance concerns Google Cloud and should not be applied as though it describes Hetzner’s billing system.
For transfer, establish the full route before ordering: the account’s stated payment details, the correct customer ID reference, your bank’s fee and the expected processing time. A manual transfer can involve steps and timing that differ from an automatically charged card. If the due date is close, check that the funds can reach Hetzner in time rather than relying on an assumed instant settlement.
Keep confirmation of the method offered and payment records with your account documents. If a payment fails, check the provider’s reason and Hetzner’s current account instructions before retrying. Repeated retries without knowing whether the first payment is pending can create confusion. The aim is to confirm both sides of the transaction, not infer the cause from a generic error message.
Review invoices and VAT details
Hetzner bills retrospectively: its payment overview says invoices are issued after use, are due immediately and must be paid within ten days. Credit card charges are automatic after invoice issue; bank transfer and PayPal require manual action. Treat the invoice as an operating task, not an annual renewal reminder. Set a reminder to inspect account notices and settle manual invoices promptly.
Check that the invoice account details and billing information match the information you intended to provide. This matters for bookkeeping and for understanding which entity is being billed. If your payment route requires a reference, use the customer ID as Hetzner instructs. Save the invoice and payment confirmation in the records you use for business or tax administration.
Hetzner states that invoices to customers in countries outside the EU are issued without VAT under its policy. This describes Hetzner’s invoice treatment; it does not determine any separate tax obligation you may have in India. If you are unsure how a foreign hosting invoice should be recorded or treated locally, ask a qualified adviser or consult the relevant current official guidance. Do not infer that a zero VAT line settles every local tax question.
An invoice can also help you compare the real cost of running the stream over time. Include the hosting charge, payment conversion or transfer fees charged by your provider, and any other costs in your own budget. Check the current Hetzner invoice and terms for your account instead of relying on an old estimate from a forum or another customer, since the service selected and billing details may differ.
Plan the encoder and media source
A Hetzner server supplies computing capacity; it does not supply a camera, microphone, playlist or other video feed. You must decide what the stream should show and how that content reaches an encoder. For a devotional channel, the source might be a prepared video or audio-and-image programme. For a news loop, it might be a sequence of graphics and clips that you are authorised to use. A VPS alone does not capture a live camera feed or create programming.
YouTube supports encoder-based streaming using software or hardware. The encoder converts your media into a format YouTube can ingest. You then configure the encoder to send the stream to the YouTube event using the stream details YouTube provides. The YouTube guide to streaming with an encoder explains the platform’s workflow. You remain responsible for preparing the media, choosing the encoder and checking that the system can sustain the intended output.
There are several possible arrangements. You might encode on a computer at your premises and send the stream onwards, or configure software on the server to encode or relay media that is already available to it. Those are different workloads. If the server is expected to encode, account for the video processing load and configure the software yourself. If it relays an encoded feed, it still needs a dependable source and a working network path. Neither arrangement is created simply by renting a server.
For examples of a software-based playlist workflow, see this guide to running a YouTube radio stream with Liquidsoap and FFmpeg. If your material is audio files, the Tamil Carnatic MP3 streaming walkthrough is a more specific example of arranging content before broadcast. These examples can help clarify the source-and-encoder distinction, but your own files, permissions and configuration still need checking.
Compare server choices against the work you intend to run: source location, encoder load, chosen resolution and frame rate, sustained network capacity, latency, monthly cost and your ability to administer and secure the machine. Hetzner’s terms put responsibility for managing and securing root and cloud servers on the customer. If you do not want to maintain server software or recover it when a process stops, that operational work should weigh as heavily as raw capacity in your decision.
Connect an encoder to YouTube Live
First confirm that live streaming is enabled on your YouTube channel. YouTube says first-time enablement can take up to 24 hours, so do this well before a planned launch. Follow the current instructions in YouTube Studio rather than assuming that creating an event alone means the channel is ready to broadcast.
Next choose the source and encoder route. A software encoder such as FFmpeg or OBS can run on a suitable computer or be configured on a server, while a hardware encoder is another route if it fits your setup. Prepare the media input first. For a prerecorded loop, verify that the files play as intended and that the playlist does not reach an unexpected end; for a live camera, confirm the device or feed is actually accessible to the machine doing the encoding.
Create or schedule the live stream in YouTube Studio and use the stream key and ingestion information YouTube supplies. Treat the key like a password: do not publish it in scripts, screenshots or public support posts. Enter it only in the encoder configuration that needs it. Then select the corresponding YouTube ingest protocol and settings supported by the encoder. YouTube documents RTMP/RTMPS ingestion and supported codecs in its recommended encoder settings.
Resolution and bitrate should match the content and what the whole route can reliably sustain. YouTube’s published H.264 recommendations include 8 Mbps for 720p at 30 or 60 frames per second, 14 Mbps for 1080p at 30 fps, and 17 Mbps for 1080p at 60 fps. These are YouTube recommendations, not a guarantee that a particular server, network path or encoding process can deliver them continuously. A lower setting that holds steadily is more useful than a higher setting that repeatedly stalls.
YouTube recommends constant bitrate encoding and a two-second keyframe interval, with the interval not exceeding four seconds. Check that your encoder’s output settings match the current platform guidance. Once you start the broadcast, look at both the encoder’s connection status and YouTube Studio’s stream health. A message that the encoder is connected does not, by itself, confirm that viewers hear the right audio or see the intended image.
Test before relying on the stream
Run a complete rehearsal before treating the setup as ready for an overnight or important broadcast. Test the actual media source, encoder, server route and YouTube event together. A short local playback test proves only that a file can play locally; it does not test the ingest connection, the stream key, the encoder settings or the path from the server to YouTube.
Use representative content. If the channel will show moving visuals, test motion rather than a static title card alone. If it will carry music, listen through the start, transitions and a longer section for gaps, clipping or unexpected silence. Check the stream from a separate viewer device where possible, because the producer’s preview may not reveal the same playback conditions as a viewer’s screen.
Observe the server and encoder while the test runs. Look for sustained processor use, memory pressure, dropped frames, reconnects and errors in the encoder log. A server that starts the stream successfully may still struggle under a longer encode or with higher resolution. If the process is interrupted, identify whether the issue was the source, encoder, server, network route or YouTube event before changing several settings at once.
The FFmpeg reconnect settings guide can help when a stream repeatedly disconnects, while the Ubuntu continuous-stream setup guide for India illustrates a different always-on operating approach. Neither removes the need to test your exact content and server. Hetzner’s terms describe an annual average network availability target of 99.9% at its data centres, but this is a stated target, not a promise of uninterrupted delivery for an individual broadcast. Your encoder, source, configuration and YouTube ingest path remain part of the chain.
Make a recovery plan before the first unattended run. Know how you will notice a stopped process, restart it, check the stream in YouTube Studio and protect the stream key if you share server access. Hetzner leaves server administration and security to the customer, so keep software updated, limit access and understand how your process starts again after a reboot. If you cannot monitor the workflow overnight, do not assume the server will correct a configuration or source problem automatically.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Which payment methods can I use from India?
Hetzner lists credit card, bank or wire transfer, PayPal and SEPA direct debit, but says available options depend on country. Check what your account actually offers; the general list does not establish what will appear for every Indian customer. Your bank or payment provider must also authorise the transaction.
Can I change my Hetzner account from EUR to USD later?
Hetzner says account currency cannot be changed after account creation. Its stated route is to open a new account and transfer products, so choose EUR or USD before signup and consult Hetzner before moving an active setup.
Does a Hetzner server provide the live video feed?
No. The server can run an encoder or relay media that is supplied to it, but it does not itself provide a camera, microphone, playlist or other content source. You need to configure both the media input and the encoder that sends the stream to YouTube.
Does Hetzner add VAT to an Indian customer’s invoice?
Hetzner says customers outside the EU receive invoices without VAT under its policy. That statement does not resolve any separate Indian tax or record-keeping obligations, so check current official guidance or ask a qualified adviser if you need advice for your situation.