We're sorry GroupDocsCloud doesn't work properply without JavaScript enabled.

Free Support Forum - groupdocs.cloud

Epub parser returns gibbrish with the text

I only want plain text extracted from a file but it gives back all the links and other random characters.I have attached the image. Here is the code

Future<String?> getParsedText(File? file, String? fileName) async {
    var accessToken = await generateJwt();
    var filePath = await uploadDocumentToCloud(file, fileName, accessToken);

    var url = Uri.parse('https://api.groupdocs.cloud/v1.0/parser/text');
    var body = jsonEncode({
      "FileInfo": {
        "FilePath": filePath,
    var headers = {
      'Content-Type': 'application/json',
      'Accept': 'application/json',
      'x-aspose-client': 'Containerize.Swagger',
      'Authorization': 'Bearer $accessToken',
    var response = await http.post(url, body: body, headers: headers);
    if (response.statusCode == 200) {
      var text = jsonDecode(response.body)["text"];
      return text;
    return null;

WhatsApp Image 2022-05-07 at 10.40.57 AM.jpeg (96.0 KB)


Please share your input document along with the excepted output. We will look into it and will guide you accordingly.

traction.zip (871.2 KB)
Extract the zip file to get the epub and the expected output in a text file.


Please try PlainText value of FormattedTextOptions.Mode property, it will help you to extract plain text.
Extract_PlainText.zip (16.3 KB)

  "FileInfo": {
    "FilePath": "Traction How Any Startup Can Achieve Explosive Customer Growth (Gabriel Weinberg Justin Mares) (z-lib.org).epub"
  "FormattedTextOptions": {
    "Mode": "PlainText"

Plain text option does not return the whole text in the epub. It’s incomplete and also contains
Evaluation only. Created with GroupDocs.Parser for .NET. Copyright 2022 Aspose Pty Ltd.
every few sentences.


We are sorry for the inconvenience. We have logged a ticket(PARSERCLOUD-329) for further investigation and rectification. We will update you as soon as possible.

Any updates? It has been more than 2 weeks


I am afraid the issue is still pending for investigation in the queue. We will share the update/ETA as soon as the investigation is completed.