SlidesGPT review:
Company, pricing & AI testing

Method: Generate the same six-slide brief using the explicit count setting and Auto separately, three fresh runs each.

Evidence: Rendered count, cover/agenda behavior, settings and every output.

Method: Provide six exact headings; compare every rendered title and position with the fixture.

Evidence: Ordered title list and position-match percentage.

Method: Request a table, chart and limitations on specified slides; count covers and agenda consistently.

Evidence: Rendered positions and screenshots of each required element.

Method: Request a fixed bullet count, word limit and prohibited phrases on designated slides.

Evidence: Bullet counts, word counts and prohibited-phrase occurrences.

Method: Supply a deliberately conflicting brief and a clear priority rule; observe whether the tool follows the rule or requests clarification.

Evidence: Conflict resolution and unsupported decisions, with original prompt.

Method: Supply a fictional brief with 20 locked facts, names, dates and amounts; compare output with an answer key.

Evidence: Correct facts out of 20, omissions and alterations.

Method: Use a brief with intentionally limited information and prohibit invented facts.

Evidence: Every unsupported factual claim and its slide location.

Method: Omit figures needed for a conclusion and explicitly prohibit estimation.

Evidence: Whether gaps are disclosed, questions are asked or numbers invented.

Method: Provide a set of controlled source URLs and require source attribution; inspect cited links and supporting passages.

Evidence: Working links, supported claims and fabricated citations.

Method: Upload an authorized synthetic PDF containing known paragraphs, tables and footnotes, when the tested tier supports it.

Evidence: Extracted facts versus fixture; missing or distorted table/footnote content.

Method: Use locked positive, negative and zero-baseline examples with known answers.

Evidence: Correct calculations, units, rounding and zero-baseline handling.

Method: Provide a synthetic dataset with totals and percentage breakdowns that must reconcile.

Evidence: Absolute errors and whether percentages/totals reconcile.

Method: Mix monthly/annual costs, two currencies and thousands/millions with explicit conversion rules.

Evidence: Unit labels, currency labels and conversion accuracy.

Method: Require a chart and table from the identical dataset.

Evidence: Every chart label/value compared with the source table.

Method: Mix achieved results, forecasts and goals, explicitly labeled in the fixture.

Evidence: Misclassification count and visibility of forecast/target labels.

Method: Generate the same brief for executives and beginners; evaluate against a rubric fixed before generation.

Evidence: Blind rubric scores for terminology, explanation and audience fit.

Method: Use a problem-evidence-options-recommendation brief and inspect the causal sequence.

Evidence: Sequence adherence, transitions and unexplained conclusions.

Method: Specify slide word limits and readability requirements on a fixed source brief.

Evidence: Words per slide, repeated content and predefined readability checks.

Method: Provide a technical passage with an answer key and ask for an accessible explanation.

Evidence: Key concepts retained and meaning-changing simplifications.

Method: Translate the same locked brief into specified languages and use qualified reviewers.

Evidence: Name/number preservation and reviewer-graded meaning, fluency and terminology.

Method: Generate short, medium and long text fixtures; inspect at fixed display dimensions.

Evidence: Clipped text, collisions and elements outside slide bounds.

Method: Assess title/body/caption styling using a predeclared readability rubric.

Evidence: Font sizes, hierarchy consistency and unreadable labels.

Method: Generate multiple slides with the same chosen theme and review spacing, color and alignment.

Evidence: Style deviations across the deck, supported by screenshots.

Method: When supported, supply a test logo, palette and fonts owned by iSync.

Evidence: Exact palette/font/logo placement checks and unsupported controls.

Method: Use five synthetic scenarios and grade supplied/generated imagery against the brief.

Evidence: Relevant images, misleading imagery and documented provenance where available.

Method: Request a table with fixed rows, columns, labels and values.

Evidence: Missing cells, changed values and visual legibility.

Method: Use time-series, categorical and proportion datasets with permitted chart types defined in advance.

Evidence: Chart-type match and whether the chosen representation misleads.

Method: Require units, labels, scales and source notes for each chart.

Evidence: Correct axes, omitted units and misleading truncation.

Method: Supply a controlled larger table and inspect both displayed and exported slides.

Evidence: Readable values, overlap and handling of overflow.

Method: Request a flowchart from a locked process with branches and exceptions.

Evidence: Correct nodes, edges, branch labels and omitted exceptions.

Method: Change a heading and reorder a section before generating the deck.

Evidence: Whether final output preserves the saved edits and order.

Method: Request a change to one slide while explicitly preserving all others.

Evidence: Target change completed and unintended changes elsewhere.

Method: Regenerate a selected element with facts and numbers declared invariant.

Evidence: Preserved facts, retained layout and unsupported changes.

Method: When offered, make and undo a sequence of edits on a disposable test deck.

Evidence: Recoverable states, restored content and lost edits.

Method: Save an authorized test deck, close the view and reopen it through the product UI.

Evidence: Content, styling and notes retained after reopening.

Method: Export an authorized test deck to PPTX on a tier that permits it; inspect it in PowerPoint or another declared viewer.

Evidence: Text, layout, charts, notes and editability versus browser output.

Method: Export the same deck to PDF and inspect every page.

Evidence: Page count, clipped elements, fonts and text selection.

Method: If available, import/export the test deck through an authorized Google Slides account.

Evidence: Layout and editability differences from the source deck.

Method: Open exported files on a second declared environment without the original fonts installed.

Evidence: Fallback fonts, missing images and broken media.

Method: Include known speaker notes and links, then inspect each supported export.

Evidence: Notes retained, links functional and content in the correct layer.

Method: Measure from submission to usable completed deck across repeated locked tasks.

Evidence: Instrumented timing, median, range and environment/tier.

Method: Run three predefined task variants three times each without selecting the best output.

Evidence: All nine results and variation in checklist scores.

Method: Record normal failures during the planned runs and exercise documented retry controls.

Evidence: Failure rate, error messages, recovery and duplicate outputs.

Method: Use increasingly long synthetic briefs within documented product limits.

Evidence: Completion, omissions, truncation and time by input length.

Method: Repeat the locked suite after a documented product update or at the scheduled retest date.

Evidence: Configuration/version evidence and comparable historical outputs.

Method: Have a first-time tester complete a declared task without assistance.

Evidence: Time, errors, help required and completed steps.

Method: Ask testers to locate slide count, theme, language and export controls that exist on the tier.

Evidence: Task completion and navigation steps.

Method: Generate, inspect and edit where supported on a declared mobile viewport/device.

Evidence: Usable controls, blocked steps and display defects.

Method: Compare displayed generation/download limits with actual behavior on the authorized tier.

Evidence: Clear limits, blocked actions and unexpected restrictions.

Method: With owner authorization, submit one ordinary support question about an observed issue.

Evidence: Response time, relevance and whether the proposed fix works.

Method: Complete the declared core workflow using only the keyboard.

Evidence: Reachable controls, focus visibility, traps and completion.

Method: Inspect the core UI and generated document with a named screen reader.

Evidence: Meaningful control names, reading order and missing labels.

Method: Measure text/background combinations on generated slides against a declared contrast threshold.

Evidence: Measured ratios and failures by element.

Method: Inspect exported reading order and alternative text where supported.

Evidence: Logical reading sequence and informative image alternatives.

Method: Inspect the UI at 200% zoom and the deck on a small screen.

Evidence: Lost controls, overlap and unreadable content.

Method: Compare the operator identity, privacy terms and in-product data notices.

Evidence: Contradictions or unclear statements, labeled as documentation findings.

Method: Create a synthetic deck and inspect default sharing controls and public/private labels.

Evidence: Who can access the deck under each available setting.

Method: Use only an explicitly disposable synthetic deck and the documented deletion workflow.

Evidence: UI confirmation and subsequent accessibility under the same account.

Method: Inspect available data-retention and model-training preferences without assuming vendor claims are verified.

Evidence: Displayed choices, changes applied and remaining uncertainty.

Method: Inspect warnings and instructions about submitting private material; submit only synthetic fixtures.

Evidence: Clear user guidance and observable controls; no security-assurance conclusion.