Here is landing page: https://finnish-streaming-dual-sub.netlify.app/ and demo video: https://www.youtube.com/watch?v=O3B7BCvd99Y

It is an open-source project, translates Finnish subtitle to other languages. Users need to register to DeepL system and get DeepL token / translation key. By this way, motivated users can get their own key and the project can live well without active maintenance from my side. Now my app gets more than 250 installations without marketting.

I'd like to raise one concern regarding the recent pricing changes. The Free and Pro tiers have been replaced by Developer and Growth, with Growth costing €29.75/month for 1 million characters. For individual language learners, 150,000 characters per month is typically more than enough — making the Growth tier feel disproportionately expensive.

Would it be possible to introduce a more accessible B2C tier? Something like a €5 base price with pay-as-you-go for extra usage would make a real difference. It would also help greatly if users could purchase translation keys via Google Pay, Apple Pay, or PayPal — credit card requirements can feel intimidating for individual users and create unnecessary friction.

I know the docs say document translation picks one source language per file.
My problem is that my files don't really have one, a single .docx might have Dutch, French, and German paragraphs mixed together, and I need the whole thing in English.

Is there a way to handle this with the API?
I know I could fall back to the regular text translation endpoint and send things chunk by chunk with source_lang left blank, but that would explode the number of calls (and the cost) pretty fast. Is there a cleaner way to do this on the document side, or is splitting the only realistic path?

Doing it by hand isn't going to scale once there's any real volume.

Has anyone done this before?

Thanks.

Either this needs to be fixed, or the settings should allow you to limit the history to a certain period of time

But it works in Internet Explorer!

What’s going wrong? If there are issues with Windows, I urge you to refund my subscription costs. There are plenty of excellent AI tools that can translate to a high standard. I no longer have time to fiddle around with this app.

Please excuse these remarks, but I’m asking for a refund of the costs and that will be that.

Thank you

🎤 Upcoming: Deep Dive into the DeepL Voice API

Our next DevTalk is coming up on May 12th, 5–6pm Berlin time with Christian Meißner Technical Lead for the DeepL Voice API.

We’ll focus on real-world implementation: how to use the Voice API in projects, real-time translation workflows, architecture decisions, SDK usage, and practical questions.

👉 If you’re building with the Voice API, exploring what’s possible, or just curious, feel free to drop questions in advance.

🛠️ Made with DeepL: VoiceBuddy

Tim shared VoiceBuddy, an open-source Windows app that provides real-time translated captions for any audio playing on your system: YouTube, Twitch, Discord, game voice chat, Zoom, podcasts, and more.

It’s a great example of what can be built with the newly released DeepL Voice API.

👉 Check it out, test it, and share feedback or questions in the thread.

💻 DeepL API Prompts: feedback wanted

Tim also shared a new GitHub repository with sample prompts, schemas, and examples for using the DeepL API with coding agents.

Since this approach is still fairly new, feedback would be very helpful, especially from anyone already using AI-assisted development tools.

💬 Ongoing API & product discussions

There’s still ongoing discussion around the Style Rules endpoint, where the API team is gathering feedback on endpoint structure, language-specific handling, formatting preferences, and developer workflows.

👀 Looking ahead

• DevTalk: Deep Dive into the DeepL Voice API → May 12

• More builder-focused discussions and project showcases coming soon

• Keep sharing what you’re building, testing, or experimenting with!

Particularly curious about if you'd consider this approach actually helpful or not 🙂

https://github.com/DeepLcom/deepl-api-prompts