Filipino data for AI training, collected to your brief
Filipino data from IndecalAI is collected or reviewed by a native Filipino speaker, not pulled from an existing archive. We work with speakers across Southeast Asia, often alongside two or three other languages in the same household, matched to your brief and checked before delivery.
What Filipino data can we produce?
Filipino data from IndecalAI is speech, text, conversational and translation data collected or reviewed by a Filipino speaker for your brief, not pulled from an existing archive.
Code-mixing with English or a neighboring language is common in everyday speech and text here, and a brief should say whether to keep that mixing or write a cleaner single-language version.
This sits across several of our services depending on what you need: data collection for raw speech or text, conversational AI data for dialogue, and translation and localization for converting between Filipino and another language.
Image and video categories on our datasets hub don't depend on language at all, so a project can combine this with visual data from the same region.
Filipino data at a glance
- Data types
- Speech, text, conversational, translation
- Services
- Data collection, Translation
- Who works on it
- Contributors from our network of 30,000+ people worldwide, matched to your brief.
- Review
- A review pass before anything is delivered.
- Your data
- NDA first, used only for the agreed scope, returned or deleted when you ask.
- First step
- A small free sample before you commit.
What to know about Filipino before you brief it
Filipino is the national language of the Philippines and is based on Tagalog, the language of Manila and the surrounding region. It is used in schools, television and government, alongside English.
In real conversation, Filipino and English mix so freely that the blend has its own name, Taglish. A model trained on pure Filipino text will often fail to handle it, so decide early whether your data should be pure, mixed, or both. Formal Filipino uses honorific particles such as po and opo for respect, and customer-facing speech depends on whether those are expected.
Languages that sit close to Filipino in script, family or region: Cebuano data, Ilocano data, Indonesian data, Malay data, Maori data and Javanese data.
Deciding what to specify for any language? The guide to speech data collection covers the choices that apply across languages, and the one on transcription for AI and for people covers how speech becomes text.
Filipino at a glance
- Language family
- Austronesian (Philippine)
- Script
- Latin letters, left to right
- Spoken mainly in
- the Philippines, with a large overseas community
- Name it in a brief
- Metro Manila speech, Taglish (Filipino-English mixing), regional Tagalog
- Its own name
- Filipino
Four ways to request Filipino data
Each links to the service that runs it, with its full scope and process.
Filipino speech data
Recorded speech in Filipino: calls, prompts and voice bot utterances, including the code-mixing with other local languages if your brief calls for it.
Filipino text data
Written Filipino: messages, reviews, tickets or chat logs, written or labeled by people who read it natively.
Filipino conversational data
Scripted or spontaneous Filipino dialogue for voice bots and support agents, including the code-mixing common in everyday conversation here.
Filipino translation
Human-verified translation between Filipino and another language, covering prompts, UI copy and training data.
What to put in a Filipino brief
Four things worth deciding before contributors start, so the first sample already looks right.
Region or dialect
Filipino is spoken mainly in the Philippines, with a large overseas community. Worth naming in a brief: Metro Manila speech, Taglish (Filipino-English mixing), regional Tagalog. Tell us the region or community you're targeting so contributors are matched to the right one.
Script or transliteration
Script for Filipino: Latin letters, left to right. Say whether you want the native script, a transliterated version, or both, especially if your downstream system only reads one.
Data type mix
Speech, text, conversational and translation can be requested together or on their own. Tell us the mix your model needs.
Volume and timeline
A rough sense of how much data and how soon lets us staff the right number of contributors from the start.
From your brief to reviewed Filipino data
One named contact owns the project from scoping to the last file.
Brief
You tell us the data type, the Filipino variety or region and roughly how much you need.
NDA and scope
We sign an NDA before any data moves, then agree the scope with you.
Free sample
We produce a small sample free, so you can check it before you commit.
Production
Contributors from our network work in our own tools, to the brief you set.
Review
A review pass runs before anything is delivered.
Delivery
The data comes to you, or moves on to another service with us.
Where Filipino data ends up
Common jobs for Filipino data. They're examples of the work, not a client list.
Voice bots and IVR
Recorded Filipino prompts and calls teach a voice bot to recognize how people actually speak, not just how a script reads.
Support chat and tickets
Everyday Filipino messages, written in the domain you work in, give a chat assistant real phrasing to learn from.
Content moderation and sentiment
Labeled Filipino posts, reviews and messages teach a model to read tone and intent correctly in this language.
Localizing a product
Translating prompts, UI copy and training data into Filipino so a product reads like it was written for that market, not machine-translated.
Off-the-shelf Filipino data, or built to your brief?
We hold around 35,000 hours of off-the-shelf speech, prompts and conversations already collected across our network, and roughly 500 hours of it is Filipino: see the Filipino speech dataset. Here's how the two paths compare.
| Topic | A typical off-the-shelf dataset | Filipino data with us |
|---|---|---|
| Already collected? | No way to know until you've already paid for it | Yes: roughly 500 hours of Filipino speech are already recorded, and we tell you what they cover before you buy |
| Fit to your brief | Built for whoever bought it first, not your exact region, register or use case | Collected or reviewed to the region, script and format you specify |
| Who else has it | The same files can be sold to more than one buyer | Custom collections are scoped to your engagement. For stock data, who else can license it is set in your licence |
| Checking the fit | You find out after you've already paid for it | A small free sample first, so you check it before committing to volume |
Filipino data terms, in plain words
General definitions. They describe the field, not a claim about us.
Where Filipino data fits
Filipino is one of 100 languages on our languages directory. You can also browse every category on the datasets hub.
Questions about Filipino data
The datasets FAQ covers questions that apply across every category.
Do you support Filipino?
Yes. Filipino is one of 100 languages in this directory, part of our wider language coverage worldwide, including deep Indian language coverage. Tell us the regional variety you need.
Do you already have any Filipino data collected?
Yes. Roughly 500 hours of Filipino speech, prompts and conversations are already recorded and ready to license. The Filipino speech dataset page has the details, and anything it doesn't cover we collect to your brief.
Can you mix regional varieties of Filipino in one project?
Yes. Tell us the mix of regions or dialects you need and we'll match contributors from our network to that brief.
Which data types are available in Filipino?
Speech, text, conversational data and translation to or from Filipino. Image and video categories don't depend on language, so Filipino speakers can also appear in those briefs on request.
Is a sample available before we commit?
Yes, a small free sample first.
Can this run alongside other languages in the same project?
Yes. Many engagements mix languages, domains and data types under one brief and one named contact, using our network of 30,000+ people across 150+ projects delivered so far.
What counts as a regional variety of Filipino?
A version of the language tied to a place or community, which can differ in vocabulary, pronunciation, formality or script from another region's variety. Name the region in your brief if it matters for your use case.
Can you handle Filipino in its native script?
Yes. Contributors work in the native script by default, with transliteration available if your project needs it instead.
Which variety of Filipino should I ask for?
Ask for the one your users actually speak. Filipino is spoken mainly in the Philippines, with a large overseas community, and the forms most worth naming in a brief are Metro Manila speech, Taglish (Filipino-English mixing), regional Tagalog. If you are unsure, describe your users and where they live, and your named contact will help you decide before collection starts.
How is Filipino written, and does it matter for the data?
Filipino data uses Latin letters, left to right. The script and its encoding affect how a model reads the data, so say in the brief which one you need and whether a romanized or transliterated version is also required.
Request Filipino data
Pick the data type, confirm Filipino as the language and a rough volume, and send it. We'll produce a small sample free before you commit.
- Your named contact replies within one business day.
- We sign an NDA before any data changes hands.
- We produce your free sample, then agree the full scope.
This opens your email app with the brief filled in. Nothing is sent until you press send. You can also use the contact page.