Support
Report a Bug
How to report a bug in Babelize: what to check first, what to include so the team can reproduce it, and where to report security vulnerabilities.
Found something broken? Help us fix it.
Before Reporting
- Check Troubleshooting for known fixes
- Try refreshing the page or clearing your browser cache
- Verify the issue in a different browser
How to Report
Email: support@babelize.co
What to Include
| Information | Why |
|---|---|
| Description | What went wrong |
| Steps to reproduce | How to recreate it |
| Expected behavior | What should happen |
| Actual behavior | What actually happened |
| Account email | To investigate your account |
| Screenshots | Visual evidence helps |
Example Report
Subject: Translation fails for large repository
Steps:
1. Create a project with repo github.com/user/large-app
2. Select English → Spanish
3. Click Run Babelize
4. Wait ~5 minutes
Expected: Translation completes
Actual: Error "Translation timed out. Please try again."
Browser: Chrome 120 on macOS
Account: user@example.comSecurity Vulnerabilities
For security issues, email support@babelize.co with subject [SECURITY].
Do not publicly disclose vulnerabilities before they're fixed.
Last updated: 2026-10-16
How is this guide?
Contact Support
Contact Babelize support at support@babelize.co: what to include, response times from same day for outages to 3 business days for questions, hours and community.
Feature Requests
How to submit and vote on Babelize feature requests, what we consider when prioritizing them, and which features are currently planned or not planned.