# Roadmap

How future work on React PDF Viewer is planned and how to propose or follow a feature.

React PDF Viewer does not publish dated commitments. Planned and requested work lives in public GitHub issues, so what is being considered is always visible and up to date.

## Follow and propose work

- **See what is requested:** browse [open feature requests](https://github.com/kiralygyula92/react-pdf-viewer/issues?q=is%3Aissue+is%3Aopen+label%3Aenhancement).
- **Propose a feature:** [open an issue](https://github.com/kiralygyula92/react-pdf-viewer/issues/new/choose) describing the problem you are solving, not only the API you would like. Upvote existing issues with a 👍 reaction instead of adding “+1” comments.
- **Know what shipped:** every release is listed in the [changelog](https://react-pdf-viewer-chi.vercel.app/react-pdf-viewer/discover-more/changelog/).

## What shapes decisions

Proposals are weighed against the project's principles: new behavior is opt-in and never changes existing defaults, the package stays free of runtime dependencies, and every feature must be accessible and covered by automated tests. Each capability page's **Limitations** section lists what is known to be missing today, with a workaround.

## Related

- [Changelog](https://react-pdf-viewer-chi.vercel.app/react-pdf-viewer/discover-more/changelog/)
- [Support](https://react-pdf-viewer-chi.vercel.app/react-pdf-viewer/getting-started/support/)
- [Features](https://react-pdf-viewer-chi.vercel.app/react-pdf-viewer/all-features/)
