Frequently Asked Questions
Straight answers about how the tools work, what results mean, how photographs are handled, and where the science comes from.
What is PhytoAssist and who is it for?
PhytoAssist is a free digital plant-health workspace that helps you go from a symptom you noticed to a reasoned, sourced explanation of what may be happening.
It is built for farmers, crop advisers, agricultural students, extension staff and plant-pathology researchers. The same records serve all of them: a farmer gets practical next steps, a student gets the disease cycle behind the symptom, and a researcher gets scientific names, statuses and sources.
Which crops are currently supported?
The encyclopedia currently covers 37 crops — cereals, vegetables, fruits, legumes, oilseeds, fiber crops, spices and tuber crops — with 58 reviewed disease records.
Coverage is strongest for the major South Asian field crops: wheat, rice, cotton, maize, tomato and potato each carry several records. The library grows record by record through editorial review rather than bulk generation, so supported crops expand gradually.
Which languages are supported and how can I request translations?
The platform is currently available in English only.
Translations are planned only once the underlying records pass their specialist review, because translating unverified content multiplies errors. If a specific language would help you, tell us through the contact page — demand helps us prioritize.
Does the tool work on mobile devices?
Yes. Every page and tool is built mobile-first and works in a phone browser — no installation is required.
Photo upload, symptom selection, results and the encyclopedia all work on small screens, including slow connections. Navigation is reachable with one hand and text sizes stay readable.
Do I need to create an account?
No. All seven tools, the encyclopedia, the FAQ and the guides are open without an account.
Sign-in exists only for administrative purposes; ordinary use is anonymous. Contributions and contact messages also work without an account — we just ask for an email so we can follow up.
What happens if the service is temporarily unavailable?
Tool pages show a clear, honest error state instead of a blank screen, and you can retry once the service recovers.
When the analysis service is busy or unreachable, each tool explains what happened and preserves your input where possible. Nothing is diagnosed in that state — we would rather show an error than a fabricated answer.
How do I identify a plant disease from a photograph?
Photograph the affected part sharply and in natural light, note the crop and plant part, then use the photo detection tool — and treat the result as a leading hypothesis, not a verdict.
A photo can show pattern, color and structure, but it cannot show the pathogen itself. That is why results list alternative explanations and, where relevant, suggest what second observation would separate them.
What parts of a plant should I photograph?
Photograph the affected organ up close (leaf, stem, fruit, root) plus a wider shot of the whole plant or field pattern — lesions on one leaf tell a different story than a distribution across a canopy.
For suspected vascular or root problems, a photo of the whole plant and, if safe to dig, the roots/crown is far more informative than more leaf pictures. Keep the same affected area in focus, not the background.
Can healthy leaves or natural variegation be mistaken for disease?
Yes — variegation, natural leaf senescence and physiological spotting are the most common false alarms, and the detector is instructed to say so rather than name a disease.
Some cultivars carry stable patterns (stripes, margins, mottling) that look viral but are genetic. Uniformity across the whole plant, presence since emergence, and absence of spread are clues pointing to a normal trait. The tool can return an explicit 'no disease detected' answer.
What if my photo is blurred or poorly lit?
The tool will tell you the image is not usable rather than guess, and suggests how to retake it.
Overexposed, shaky or very distant photos are the main reason analyses fail. Take photos in diffuse daylight, hold the camera steady, and fill the frame with the symptom. A better photo genuinely changes the quality of the answer.
Can two diseases produce the same symptoms?
Yes, frequently — that is why results show differential notes and alternative possibilities instead of a single name.
Leaf spots, yellows, wilts and rots each converge from several unrelated causes (fungi, bacteria, viruses, nematodes, abiotic stress). Distinguishing them often needs a sign the photo cannot show: spore mass color, vascular browning, bacterial ooze or lab culture.
Can nutritional deficiencies resemble fungal infections?
They can, and they are among the most common confusions — nitrogen, iron and magnesium symptoms can closely mimic early leaf diseases.
Distribution is the best separator: deficiencies usually follow a pattern tied to leaf age or field position (old leaves first, or worst in wetter patches), while infections often start as discrete lesions that expand and may carry spore-bearing centers. See the symptom guide for a worked comparison.
How does PhytoAssist distinguish disease from healthy tissue?
It looks for the visual evidence a record documents — lesions with defined edges, pustules, colonies, vascular discoloration, malformations — and separates that from normal color and texture variation.
When the evidence is insufficient the result says so explicitly. A healthy leaf is never scored as a disease, and an ambiguous photo produces a request for a better observation instead of a guess.
What should I do when the system cannot identify a problem?
Retake the photo with the improvements the tool suggests, or describe the symptoms in the symptom-based tool, which works from your description instead of an image.
If both approaches stay inconclusive, the honest answer is that the observation so far cannot separate the candidates — that is the moment to scout a second time, or to involve a local lab or extension officer.
Does the platform diagnose insect, mite or herbicide injury?
It flags likely non-pathogen causes — insect feeding, mite damage and chemical injury patterns — but it does not identify the specific pest or herbicide.
Distinctive chewing patterns, stippling, distortion or drift patterns are reported as 'consistent with non-disease injury' with the reasoning. Confirming the exact culprit needs field inspection or, for herbicide injury, application records.
Why might similar-looking lesions have different causes?
Because necrosis is a plant response, not a pathogen signature — several unrelated organisms and stresses can trigger the same browning pattern.
What separates them is usually not the lesion itself but its companions: the presence of fruiting structures, ooze, a margin color, the speed of expansion, or which leaf age is affected first. Guides for the common confusions are in the symptom section.
What is the difference between disease identification and pathogen identification?
Disease identification names the syndrome (e.g. 'wheat leaf rust'); pathogen identification names the organism (e.g. Puccinia triticina).
The syndrome is what you see; the organism is the cause. Records are linked so you can move from one to the other, but they are separate questions — one disease can be caused by different organisms in different regions, and one pathogen can cause different diseases.
How do pathogen names and synonyms change over time?
Names change as taxonomy is revised, so records carry accepted names, synonyms and common aliases — and an explicit note when a name is contested.
When a name changes, older literature uses the old name. The pathogen profiles list synonyms so you can search both. Where a forma specialis or pathovar assignment is uncertain, the record says so instead of forcing a name.
Why does PhytoAssist ask for crop and location?
Crop narrows the candidate diseases dramatically, and location determines which weather-driven risks are actually relevant this week.
The same lesion means different things on wheat and on cotton, and rust risk in one district is not rust risk in another. Location is used only for the analysis you request — it is not stored with your photos or shared.
What is the difference between disease incidence and severity?
Incidence is the share of plants affected; severity is how much of each affected plant (or canopy) is damaged.
A disease can be widespread but mild (high incidence, low severity) or concentrated but devastating. Management thresholds in most crops are expressed in both terms, and mixing them up leads to wrong spray or no-spray decisions.
Why might a severity result differ from laboratory measurements?
The severity tool produces a visual estimate from a photo; lab and image-analysis methods measure the same tissue differently, so the numbers will not match exactly.
The result is deliberately reported as a qualitative grade rather than a precise percentage. For trials, insurance or certification, use a documented assessment method — the visual grade is a scouting aid, not a measurement standard.
What is disease risk and how is it estimated?
Risk here means how favorable current and forecast weather are for specific diseases, based on published epidemiological models and meteorological data.
The risk tool evaluates temperature and leaf-wetness/humidity conditions against the known infection windows of each disease for your location and reports whether conditions fall inside them. It is an environmental context layer, not a detection of disease.
Does a high disease-risk indication mean my field is infected?
No. High risk means the weather favors infection if inoculum is present — the field itself may still be healthy.
Risk answers 'should I scout now and would a protectant decision be justified?', not 'is my crop diseased?'. Combine it with what you actually find in the field before acting.
Why should crop variety and growth stage be recorded?
Because susceptibility and symptom expression both change with variety and stage — the same pathogen looks different on a seedling and a flowering plant.
Growth stage also drives epidemiology: many diseases only become economically important near flowering or grain fill. Recording stage and variety makes results, contributions and comparisons meaningful.
How should I interpret a probable diagnosis with alternative possibilities?
Treat the top result as the explanation to check first, not the answer — the listed alternatives tell you what observation would confirm or rule it out.
A good workflow: read why the leading candidate fits, then specifically look for the evidence that would distinguish it from the first alternative (spore color, ooze, distribution). If you cannot distinguish them, say so when consulting anyone.
What does the disease-management section mean by IPM?
Integrated Pest Management: combining resistant varieties, cultural practices, biological options and — only when justified — chemical tools, instead of relying on a single method.
In practice: choose resistant varieties first, break the cycle with rotation and field hygiene, manage the canopy and irrigation to shorten leaf wetness, monitor before acting, and rotate modes of action when chemical use is necessary. Management topics in the encyclopedia follow this structure.
How does the crop rotation planner account for shared host pathogens?
It groups crops by the pathogens and pathogen types they share, so a suggested rotation does not simply swap one host of the same organism for another.
Botanical family relationships matter here — rotating tomato after potato does little against shared soilborne problems. The planner flags these shared-host situations instead of presenting a naive crop swap.
Are my uploaded plant photographs stored?
Photos sent for analysis are processed to produce your result and are not kept afterwards; files uploaded through the contribution and contact forms are stored privately and reviewed by the team.
Analysis requests log technical metadata (timing, token counts) without the image, the prompt or your identity. Contribution and contact attachments go to a private storage area that only administrators can open — they are never published without your explicit consent.
Can I delete my records or request data removal?
Yes. Write to us through the contact page and we will remove your submission data.
There is no user profile to delete — ordinary tool use leaves no account and no stored images. Deletion requests cover contribution submissions, contact messages and newsletter subscriptions.
How do I report a wrong or incomplete result?
Use the feedback panel that appears under every result, or write to us through the contact page for anything that needs a longer explanation.
Feedback ratings and comments are reviewed by the team and inform record corrections. A wrong result is treated as a content problem to fix, not as noise.
How can I contribute field observations responsibly?
Only share material you own or have permission to share, describe the crop, region and conditions as precisely as you can, and note that everything is reviewed before anything is published.
The contribution page limits uploads to five files of 5 MB each, and every file is validated server-side before it is stored. Location is described at a level you are comfortable with — never publish coordinates of someone else's field.
Where does the disease encyclopedia obtain its information?
From a fixed source registry of authoritative plant-health references — EPPO, CABI, APS, FAO and university extension publications — with each record citing the sources it used.
Records never cite a source they did not draw from, and claims without reliable support are marked as not established rather than filled in. Every record shows its review status and last substantive update.
How often are disease records reviewed?
Records are re-reviewed when the underlying science, nomenclature or regional relevance changes — and every change updates the record's 'last reviewed' date.
We do not bump dates without substance. New records enter with an 'editor review pending' status and are progressively checked by plant-health specialists; that status stays visible until review is complete.
How can I compare symptoms across disease records?
The encyclopedia's symptom themes group records by what you actually see — leaf spots, rust pustules, powdery growth, wilts, rots, yellows and more.
Open a theme to see every record whose symptoms match it, which is the fastest way to build a differential list for an observation.
How do I contact support or submit a correction?
The contact page routes product support, issue reports, plant-pathology questions, collaboration offers and content corrections to the team.
Corrections that change a record's content are handled through editorial review — the record keeps its history and its sources stay traceable.
What information should be included in a crop disease report?
Crop and variety, growth stage, the plant part affected, what you see (and since when), the district or region, recent weather, and any management already applied.
Photos of the affected part plus a whole-plant view make a report far more useful. When reporting to a lab or extension service, include the same fields.
Can I use the encyclopedia for education and agricultural extension?
Yes — that is what it is for. Use and share the records in teaching, training and extension work, with attribution to PhytoAssist.
Content is provided for educational use; check each record's review status before relying on it in formal material, and prefer linking to the live page so readers always see the current version.
Does geographical location change disease risk?
Yes — the same crop faces different diseases in different regions, and weather-driven risk shifts week to week within a region.
The risk tool uses your actual location for its meteorological calculation and says so plainly; it does not guess a region from your timezone. Where region-specific official guidance exists in a record, it is labeled as such.
Are chemical control recommendations specific to my country?
No — records name active-ingredient classes and timing only, never doses, brands or country-specific registrations.
Which products are registered, at what dose, and with what pre-harvest intervals is decided nationally. Always follow the product label and your local extension service; the encyclopedia deliberately does not substitute for either.
Does PhytoAssist replace field scouting and laboratory testing?
No. It sharpens scouting and helps you decide when lab testing is worth it — it does not replace either.
Photo-based analysis cannot see inside tissue, culture a pathogen, or sequence anything. Results are designed to say when laboratory confirmation would change the decision, and to make your scouting observations more structured.