Persistent source language selection independent of interface/output language

Feature Requests
,
1

:rocket: Feature Request

Feature request: Persistent source language selection independent of interface/output language

Many multilingual users—especially professionals and students—prefer accessing English-language scientific papers and global sources (e.g., PubMed, NEJM) even when their preferred interface and output language is Spanish or another language. Currently, to force searches to use English sources while keeping answers in Spanish, one must specify this preference at the start of every new chat. There is no persistent setting to automate this; only the interface and answer language can be set in the profile.

Suggested improvement:
Add an option in account/profile settings to always prioritize (or exclusively search) sources/web content in a chosen language (e.g. “always search in English”) regardless of the language used in the query or the interface/output language, while allowing answers to remain in the user’s chosen language.

This would:

  • Greatly improve workflow for users who want international/English scientific evidence but explanations in their native language.

  • Remove repetitive prompting and potential for inconsistent results.

  • Bring Perplexity ahead of competitors in usability for cross-lingual research and medical/scientific consultation.

:magnifying_glass_tilted_left: Problem Statement

What problem or limitation does this feature aim to solve? Please describe the issue you’re facing and how this feature would help.

:light_bulb: Proposed Solution

Describe how this feature should work. If possible, provide an example or use case demonstrating how it would be used.

:pushpin: API Impact

  • Which API component is affected? [e.g., chat completions, retrieval, search filters]
  • Is this related to a specific model? [e.g., Sonar Deep Research]
  • Would this require new API parameters or changes to existing ones?

:counterclockwise_arrows_button: Alternatives Considered

Have you explored any workarounds? If so, what were they, and why are they insufficient?

:paperclip: Additional Context

Add any other relevant information, links, or screenshots that can help us better understand your request.

:e_mail: For direct inquiries, please reach out to api@perplexity.ai

2

This forum is focused on the developer community (API, integrations, and technical issues), not core product features or app suggestions.

For feature requests like this one, please share your idea directly in the official Perplexity Discord server instead:

:backhand_index_pointing_right: discord.gg/perplexity-ai