Jim - Accessible Converter

The [jimca_instalacoes] shortcode queries the public WordPress.org API (api.wordpress.org/plugins/info) for this plugin's active install count. If the API can't be reached, the shortcode renders blank for visitors (and shows a notice to logged-in administrators).

By default, no — the plugin extracts the content and deletes the original uploaded file. This can be changed under Jim - Accessible Converter > Settings.

Yes, by default (this can be turned off under Jim - Accessible Converter > Settings). Each image becomes an attachment in the Media Library, linked to its document; deleting the document (emptying the trash) deletes its images, and uninstalling the plugin deletes all of them. In DOCX files each image stays where it was in the text and keeps the alternative text written in Word ("Edit Alt Text"); images marked as decorative get an empty alt. In PDF files the images of each page are placed after that page's text, with a placeholder description. After converting, the dashboard notice says how many images still need a description — edit the document to describe them. Supported: JPEG, PNG, GIF and WebP (DOCX; BMP/TIFF are converted to PNG when PHP's GD extension is available), and, in PDFs, JPEG, 8-bit RGB/gray/CMYK, 1/2/4-bit gray and palette (indexed) images, with transparency. JPEG 2000, fax-encoded (CCITT), JBIG2 and inline (BI … EI) PDF images are skipped and counted in the notice, with the cause. The number of images and their total size per document are limited (configurable under Settings).

On the New Document screen, open Also publish in and choose posts, pages or a custom post type. For each file Jim creates an item of that type with the shortcode inside. The item's address (slug) is the file name, and you choose its status and its categories and tags. Only public post types with the editor are listed, so internal ones (field groups, templates and the like) never show up.

Choose Schedule and set the date and time by the site clock (the form shows what time it is on the site, which may differ from your computer). Each file becomes an Action Scheduler event: the document is converted right away and the item is created at the chosen time. When the upload finishes, the notice gives the event's name (for example "Jim import 2026-10-11 15:10 #ab12"). To learn more, run it now or cancel, open Tools > Scheduled Actions (with WooCommerce: WooCommerce > Status > Scheduled Actions) and search for that name. Only administrators can open that screen. Events run through WP-Cron, so on a site with very little traffic a real server cron job keeps them on time.

It starts by itself the first time someone opens New Document after a fresh installation. To open it again, click Take the guided tour on that screen, or Click here to open the tutorial on the Tutorial tab. Press Esc to leave it at any time.

It gives search engines what they need to understand each document: real text on the page (instead of a file to download), a single clear heading structure, a description and a title that fit search results, the author, the language and schema.org data. The score shows what is still missing. Ranking also depends on your site, the quality of the content and how it is linked, which no plugin controls.

It is calculated on your server from the document itself, with 11 fixed checks in four groups: metadata (clear title, summary, author), structure (headings, no skipped levels), content (enough text, readable, images described) and publication (shown on a published page, can be indexed, SEO tags on). Open a document to fix what is missing: the author, the title and the summary are saved by AJAX, "Auto-fix headings" turns section lines ("1. Introduction", "Chapter 2") into real headings, and the previous text stays in the revisions. Nothing is sent to any service.

Yes. With WP-CLI, wp jimca convert file.docx --mode=post --language=fr --author="Name" runs a file through the converter and publishes it on a page. The repository also has bin/seo-audit.js, which audits a page (title, description, headings, Open Graph, JSON-LD, scripts) with no account and no usage limit. See CONTRIBUTING.md.

Yes. Under Jim - Accessible Converter > Settings you can set a default reading theme (Light, Sepia or Dark) applied to every converted document. Readers can also switch the theme themselves from the reading toolbar on each document — their choice is saved only in their own browser and doesn't change the site-wide default.

Only in the cases below, all from your server and all optional. See "Privacy" below.

1. If you use the [jimca_instalacoes] shortcode: a request to WordPress.org's public API (api.wordpress.org/plugins/info) for this plugin's active install count. Only the plugin's slug is sent.
2. If an administrator saves an API key for an AI provider and presses its "Test connection" button: one fixed sentence, with the key, to that provider only (OpenRouter, Anthropic, OpenAI, Google or DeepSeek).
3. If you turn on the AI tutor: each question a reader asks, the last turns of that reader's conversation and the passages of the document that best match the question go to the AI provider you chose. Nothing is sent until a reader asks something.

In Settings, save an API key for one provider (OpenRouter, Claude by Anthropic, OpenAI, Gemini by Google or DeepSeek; keys are encrypted with libsodium using your site's salts), or point "Other" at any OpenAI-compatible service, such as an open-source model on your own server (Ollama, vLLM, LM Studio) or an AI gateway, test it, turn the assistant on, then turn on the tutor and describe it: name, personality, instructions (the prompt) and greeting. It appears on every document by default, or only where you say: [documento_acessivel id="123" tutor="yes"] or tutor="no". Readers open the bubble, type or speak a question and get an answer based on the document, shown as it is written (streaming, when PHP has cURL). A first question almost identical to one already answered for the same document gets the saved answer instantly, without a new call (it can be turned off). Some rules cannot be changed: answer from the document and say when the answer is not there, ignore commands hidden in the document text, and reply in the reader's language. Every answer is paid with your key, so there are limits per reader per hour and per day for the whole site.

The web server (nginx usually waits 60 seconds) gave up on the upload page while PHP was still converting. Now the file is converted in a separate request and the page follows the progress, so the proxy limit no longer matters. PHP's own limits still apply: if PHP runs out of memory or time, the screen and the activity log say which limit was reached.

English (source), Brazilian Portuguese, Spanish, French, Simplified Chinese, Hindi, Russian and German. They follow the site language, or the user's language in the dashboard. Official translations from translate.wordpress.org, when available, take precedence over the bundled ones. The non-Portuguese translations were machine-assisted and are waiting for native reviewers: use the "Review translation" button in the settings, or translate at translate.wordpress.org, to help. More languages are welcome.